Triple
T5982876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urga |
E133159
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Ikh Khüree |
E558007
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ikh Khüree | Statement: [Urga, alternativeName, Ikh Khüree]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ikh Khüree Context triple: [Urga, alternativeName, Ikh Khüree]
-
A.
Khorol
Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
-
B.
Bayan-Ölgii
Bayan-Ölgii is a western Mongolian province known for its predominantly Kazakh population, rich nomadic culture, and dramatic Altai Mountain landscapes.
-
C.
Tashanta–Tsagaannuur
Tashanta–Tsagaannuur is a remote road border crossing point in the Altai region that connects Russia with Mongolia.
-
D.
Selenge
Selenge is a northern Mongolian province (aimag) known for its agricultural lands and strategic location along the border with Russia.
-
E.
Niislel Khüree
chosen
Niislel Khüree was the historical name of Mongolia’s capital city, now known as Ulaanbaatar, during its period as a major religious and political center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6a9f2c8190b900cd7e3ab9fe42 |
completed | March 22, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1250912b48190a10dfdcc9b5a93e2 |
completed | March 23, 2026, 11:33 a.m. |
Created at: March 22, 2026, 4:04 p.m.