Triple
T37570631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-French partition of Borgu |
E934678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international territorial agreement |
C18481
|
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: international territorial agreement Context triple: [Anglo-French partition of Borgu, instanceOf, international territorial 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.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
-
C.
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.
-
D.
border treaty
chosen
A border treaty is a formal agreement between two or more states that defines, clarifies, or adjusts their mutual territorial boundaries and the rules governing them.
-
E.
private international law instrument
A private international law instrument is a legal tool—such as a treaty, regulation, or convention—that coordinates which jurisdiction’s laws and courts apply to cross-border private disputes and how foreign judgments are recognized and enforced.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.