Triple
T23405747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet–Mongolian border agreements (20th century) |
E559928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border delimitation agreements |
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: border delimitation agreements Context triple: [Soviet–Mongolian border agreements (20th century), instanceOf, border delimitation agreements]
-
A.
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.
-
B.
land border
A land border is a defined line on the Earth's surface that separates the territories of two adjacent states or regions across contiguous land.
-
C.
political boundary
A political boundary is an officially recognized dividing line that separates the geographic areas of different political entities, such as countries, states, or municipalities, defining the limits of their jurisdiction and authority.
-
D.
border territory
A border territory is a geographic area situated along the boundary between two or more political entities, often characterized by heightened strategic, cultural, and economic significance.
-
E.
political border
A political border is an officially recognized dividing line that separates the geographic territories and jurisdictions of different political entities, such as countries, states, or regions.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:38 p.m.