Triple
T22568124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Örgöö |
E558006
|
entity |
| Predicate | historicalNameOf |
P65
|
FINISHED |
| Object | Urga |
—
|
NE NERFINISHED |
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: Urga | Statement: [Örgöö, historicalNameOf, Urga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Urga Context triple: [Örgöö, historicalNameOf, Urga]
-
A.
Urga
chosen
Urga is the historical name of Mongolia’s capital city, now known as Ulaanbaatar.
-
B.
Bulganin
Bulganin is the surname of Nikolai Bulganin, a prominent Soviet politician who served as Premier of the Soviet Union during the 1950s.
-
C.
Yabgu
Yabgu was a high-ranking Turkic noble title, often designating a semi-independent ruler or viceroy governing frontier or subordinate territories within a larger khaganate.
-
D.
Ögedeid
Ögedeid refers to the lineage or ulus of Ögedei Khan, the third son of Genghis Khan and second Great Khan of the Mongol Empire, whose descendants held significant power within the empire’s ruling structure.
-
E.
Tsaagan
Tsaagan is a genus of small, carnivorous dromaeosaurid theropod dinosaur known from Late Cretaceous deposits of Mongolia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fabb9f081908c33c8e2ddf18047 |
completed | April 29, 2026, 1:32 a.m. |
Created at: April 16, 2026, 8:52 p.m.