Triple
T35549859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Mexico–Canada Agreement region (US) |
E1027325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | party to international trade agreement |
C7269
|
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: party to international trade agreement Context triple: [United States–Mexico–Canada Agreement region (US), instanceOf, party to international trade agreement]
-
A.
party to an international treaty
chosen
A party to an international treaty is a state or international organization that has formally consented to be bound by the treaty’s terms in accordance with international law.
-
B.
international agreement package
An international agreement package is a bundled set of formally negotiated documents, terms, and supporting materials that collectively define and govern a cross-border accord between participating entities or nations.
-
C.
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.
-
D.
protocol to an international treaty
A protocol to an international treaty is a supplementary legal instrument that amends, elaborates, or adds specific obligations or procedures to an existing treaty while remaining legally linked to it.
-
E.
bilateral trade association
A bilateral trade association is an organization formed between two countries to promote, facilitate, and regulate trade and economic cooperation through agreements, advocacy, and joint initiatives.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.