Triple
T3272908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möngke Khan |
E68690
|
entity |
| Predicate | heldKurultai |
P11003
|
FINISHED |
| Object | Kurultai of 1251 electing him Great Khan |
—
|
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: Kurultai of 1251 electing him Great Khan | Statement: [Möngke Khan, heldKurultai, Kurultai of 1251 electing him Great Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldKurultai Context triple: [Möngke Khan, heldKurultai, Kurultai of 1251 electing him Great Khan]
-
A.
heldCouncil
chosen
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
B.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
C.
holdsSummit
Indicates that an entity organizes and conducts a formal summit meeting or conference with others.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff6308881908886a44804a0bb09 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.