Triple
T28492676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulugh Muhammad |
E721017
|
entity |
| Predicate | successorAsKhanOfKazan |
P86701
|
FINISHED |
| Object | Mahmud of Kazan |
—
|
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: Mahmud of Kazan | Statement: [Ulugh Muhammad, successorAsKhanOfKazan, Mahmud of Kazan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKhanOfKazan Context triple: [Ulugh Muhammad, successorAsKhanOfKazan, Mahmud of Kazan]
-
A.
successorAsEasternRuler
chosen
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
B.
successorAsValideSultan
Indicates that one entity became the next legitimate or officially recognized sultan after another entity.
-
C.
successorAsLatinEmperor
Indicates that one entity became the next holder of the title of Latin Emperor after another entity.
-
D.
predecessorAsSultan
Indicates that one entity previously held the position of sultan before another entity, directly preceding them in that role.
-
E.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 28, 2026, 3:02 a.m.