Triple
T22653868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Монгол Улсын Ерөнхий сайд |
E559169
|
entity |
| Predicate | officeHolderTitleInMongolian |
P67727
|
FINISHED |
| Object | Монгол Улсын Ерөнхий сайд |
—
|
LITERAL 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: Монгол Улсын Ерөнхий сайд | Statement: [Монгол Улсын Ерөнхий сайд, officeHolderTitleInMongolian, Монгол Улсын Ерөнхий сайд]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderTitleInMongolian Context triple: [Монгол Улсын Ерөнхий сайд, officeHolderTitleInMongolian, Монгол Улсын Ерөнхий сайд]
-
A.
officeHolderTitleInBulgarian
Indicates the official title or designation of an office holder as expressed in the Bulgarian language.
-
B.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
C.
officeHolderTitleInHungarian
Indicates the official title or designation of an office holder expressed in the Hungarian language.
-
D.
officeHolderTitleInPinyin
Indicates the pinyin (romanized Chinese) form of the title held by an office holder.
-
E.
hasNameInMongolian
chosen
Indicates that an entity is associated with a specific name expressed in the Mongolian language.
- F. None of above.
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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17659e4dc81909cf6943c1c986ef9 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.