Triple
T18434125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia Treaty Process |
E450348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty negotiation framework |
C2127
|
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: treaty negotiation framework Context triple: [British Columbia Treaty Process, instanceOf, treaty negotiation framework]
-
A.
multilateral negotiation process
chosen
A multilateral negotiation process is a structured series of interactions among three or more parties with differing interests, aimed at reaching mutually acceptable agreements through communication, bargaining, and compromise.
-
B.
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.
-
C.
treaty practice
Treaty practice is the body of procedures, behaviors, and interpretive approaches that states and international actors consistently follow in negotiating, applying, and understanding treaties.
-
D.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
E.
treaty implementation rules
Treaty implementation rules are the detailed legal and administrative provisions that translate a treaty’s general obligations into specific, enforceable procedures and standards within a jurisdiction.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:28 a.m.