Triple
T38661709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalkha Mongols |
E940350
|
entity |
| Predicate | historicalRulingEliteIn |
P172518
|
FINISHED |
| Object | Outer Mongolia |
E23408
|
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: Outer Mongolia | Statement: [Khalkha Mongols, historicalRulingEliteIn, Outer Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRulingEliteIn Context triple: [Khalkha Mongols, historicalRulingEliteIn, Outer Mongolia]
-
A.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
B.
hasRulingPeople
chosen
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
C.
rulingDynasties
Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
-
D.
ethnicGroupOfRulers
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
E.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
- F. None of above.
Provenance (4 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02ff7de1d881909c29729f2a771381 |
completed | May 12, 2026, 10:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a420e025bf8819098ee83e1b2e6a3f1 |
completed | June 29, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_6a02fd1c45c48190bf9dbd91acaeee9f |
completed | May 12, 2026, 10:12 a.m. |
Created at: May 3, 2026, 4:33 p.m.