multi-stage-cascade-extraction

Featured

Run a multi-stage extraction cascade (mention detection, document-level coreference clustering, optional saliency judgment, N-ary relation/triple extraction) directly over a paper's full text — covers SciERC, SciREX, and NLP Contribution Graph. Use this whenever cross-sentence or document-level entity/relation extraction is needed (e.g. SciREX-style Task-Dataset-Metric-Score tuples); do NOT use unit-classification for this, since these methods reason over the whole document's mentions, not independently-classified sentence units.

Data & Documents 392 stars 34 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
86
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
76
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Multi-Stage Cascade Extraction Mention detection → coreference clustering → [saliency] → relation extraction, all stages consuming the full prior stage's output. Covers SciERC/SciREX/NLP-Contribution-Graph — three methods with different stage counts but the same "consume-the-full-prior-layer" structure (graph correction S6: merged under the unifying rule "same action-sequence length → mergeable via parameterization"). ## Execution Subagent — spawned via spawn-agent skill. ## Why Direct From paper-fetch, Not Through unit-segmentation This cascade discovers its own mention spans over the whole document rather than consuming pre-segmented sentence/clause units — sentence-level segmentation is the wrong granularity for a method whose relations are 99% cross-sentence (SciREX's own reported figure). This is a deliberate graph choice, not an oversight — see spec §5's flagged note before "fixing" this dependency. ## Errors Compound Stage-Over-Stage NLP Contribution Graph's own reported consistency figures fall from stage to stage (67.92% → 41.82% → 22.31%) — this is the shared risk profile of this whole method family, not specific to one method. Producing every stage's intermediate output (not just the final relations) is what makes this compounding visible and debuggable. <!-- BEGIN available-tables (generated) --> ## Available SOPs | SOP | When to use | | --- | --- | | spawn-agent | Spawn a customized CC subagent with full MCP tool access. | <!-- END available-tables (...

Details

Author
yogsoth-ai
Repository
yogsoth-ai/de-anthropocentric-research-engine
Created
6 months ago
Last Updated
1 weeks ago
Language
HTML
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

multi-stage-cascade-extraction

Run a multi-stage extraction cascade (mention detection, document-level coreference clustering, optional saliency judgment, N-ary relation/triple extraction) directly over a paper's full text — covers SciERC, SciREX, and NLP Contribution Graph. Use this whenever cross-sentence or document-level entity/relation extraction is needed (e.g. SciREX-style Task-Dataset-Metric-Score tuples); do NOT use unit-classification for this, since these methods reason over the whole document's mentions, not independently-classified sentence units.

1 Updated 1 weeks ago
yogsoth-ai
AI & Automation Listed

extract-structured-bundle

Finalize a paper's verified reading output into the exact bundle schema (problem/method/key_result/limitation, each with a source_anchor) that all downstream fact-checking and article-drafting sops consume. Use this as the last step of the deep-read strategy, after third-pass-verify, whenever you need to hand off a finished bundle to quality-assurance or audience-first-writing.

1 Updated 1 weeks ago
yogsoth-ai
AI & Automation Listed

unit-classification

Classify each pre-segmented text unit independently against a fixed label set (Argumentative Zoning, CoreSC, PubMed-RCT, Swales move/step, CODA-19, TDMS, or CSFCube's facet labels), single-layer with no cross-unit dependency. Use this after unit-segmentation has split the text, whenever a sentence- or clause-level rhetorical/functional classification is needed; do not use this for methods requiring document-level coreference reasoning (see multi-stage-cascade-extraction instead).

1 Updated 1 weeks ago
yogsoth-ai