Triple
T248495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes–St. Lawrence River Basin Water Resources Compact |
E5089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water resources agreement |
C964
|
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: water resources agreement Context triple: [Great Lakes–St. Lawrence River Basin Water Resources Compact, instanceOf, water resources agreement]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
watershed association
A watershed association is a community-based organization dedicated to protecting, restoring, and sustainably managing the land, water, and ecological resources within a specific watershed.
-
C.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
political agreement
chosen
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
E.
river
A river is a natural flowing body of water, usually freshwater, that moves continuously along a defined channel from higher elevations toward lower ones, often emptying into a sea, lake, or another river.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.