Triple
T5487295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Regional Commission |
E123614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. federal–state partnership |
C1091
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: U.S. federal–state partnership Context triple: [Appalachian Regional Commission, instanceOf, U.S. federal–state partnership]
-
A.
United States federal–state initiative
A United States federal–state initiative is a collaborative program or policy jointly designed, funded, and implemented by the federal government and one or more state governments to address shared public objectives.
-
B.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
C.
bi-state agency
chosen
A bi-state agency is a governmental or quasi-governmental organization jointly created and governed by two neighboring states to manage shared resources, infrastructure, or regulatory responsibilities across their common jurisdiction.
-
D.
interstate compact
An interstate compact is a formal, legally binding agreement between two or more U.S. states, approved by their legislatures (and often by Congress), to cooperatively address shared problems or manage common resources.
-
E.
federal unit
A federal unit is a constituent political entity, such as a state or province, within a federal system that shares sovereignty with a central government while retaining certain autonomous powers.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:10 p.m.