Triple
T22846519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashanta–Tsagaannuur |
E566234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russia–Mongolia border crossing |
C46912
|
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: Russia–Mongolia border crossing Context triple: [Tashanta–Tsagaannuur, instanceOf, Russia–Mongolia border crossing]
-
A.
region of Mongolia
A region of Mongolia is a geographically defined area within the country characterized by distinct physical landscapes, cultural practices, and administrative or historical significance.
-
B.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
-
C.
border city
A border city is an urban settlement located near or directly on the boundary between two or more political or geographic regions, serving as a hub for cross-border movement, trade, and cultural exchange.
-
D.
United Nations demarcation line
A United Nations demarcation line is an internationally recognized boundary established or supervised by the UN to separate conflicting parties or territories, typically as part of a ceasefire or peacekeeping arrangement.
-
E.
rail border crossing
A rail border crossing is a designated point where railway lines intersect an international boundary, enabling the controlled movement of trains, cargo, and passengers between countries.
- F. None of above. chosen
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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:36 p.m.