Triple
T24030574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toghrul |
E595091
|
entity |
| Predicate | roleInMongolUnification |
P114417
|
FINISHED |
| Object | initial protector and patron of Temujin |
—
|
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: initial protector and patron of Temujin | Statement: [Toghrul, roleInMongolUnification, initial protector and patron of Temujin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMongolUnification Context triple: [Toghrul, roleInMongolUnification, initial protector and patron of Temujin]
-
A.
roleAtMongolCourt
Indicates a person's specific position, function, or status within the Mongol imperial court.
-
B.
pre-MongolRuler
Indicates that one entity served as a ruler before the period of Mongol domination or rule over the relevant region.
-
C.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
D.
roleInDynastyFounding
chosen
Indicates the role or contribution an entity had in the founding or establishment of a particular dynasty.
-
E.
viewOnMongols
Indicates the stance, opinion, or perspective that one entity holds regarding the Mongols.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76fbedc8190a2f936729cb69993 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:55 p.m.