Triple
T17277712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesapeake Bay Commission |
E419434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interstate legislative commission |
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: interstate legislative commission Context triple: [Chesapeake Bay Commission, instanceOf, interstate legislative commission]
-
A.
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.
-
B.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
C.
interstate convention
An interstate convention is a formal gathering of representatives from multiple states convened to negotiate, draft, or coordinate agreements, policies, or constitutional changes on matters of shared concern.
-
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.
interagency committee
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.