Triple
T26989633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | interstate compact council |
E679831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-state council |
C21936
|
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: multi-state council Context triple: [interstate compact council, instanceOf, multi-state council]
-
A.
bi-state agency
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.
-
B.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
C.
interstate council
chosen
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
-
D.
confederation of states
A confederation of states is a union of sovereign states that voluntarily cooperate on certain common matters through a central body that has limited authority and depends on the member states for implementation and enforcement.
-
E.
proposed U.S. state
A proposed U.S. state is a defined geographic and political region that has been formally or informally suggested for admission to the United States as a new state but has not been granted statehood.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:51 a.m.