Triple
T22593750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulaanbaatar Railway |
E574617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongolian–Russian joint venture |
C46552
|
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: Mongolian–Russian joint venture Context triple: [Ulaanbaatar Railway, instanceOf, Mongolian–Russian joint venture]
-
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.
province of Mongolia
A province of Mongolia is a primary administrative division of the country, governed by a local authority under national law and encompassing multiple districts, settlements, and geographic regions.
-
C.
Mongol imperial council
The Mongol imperial council was a high-level advisory and decision-making body of Mongol rulers, composed of princes, generals, and nobles who deliberated on matters of war, governance, succession, and law.
-
D.
India–Russia military cooperation activity
India–Russia military cooperation activity encompasses the joint defense initiatives, arms trade, technology transfers, training exercises, and strategic collaborations undertaken between India and Russia to enhance their mutual security and military capabilities.
-
E.
China–Singapore cooperative project
A China–Singapore cooperative project is a jointly planned and implemented initiative between Chinese and Singaporean entities aimed at promoting mutual economic, technological, cultural, or infrastructural development.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 2:49 p.m.