Triple
T31631222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasr ibn Sayyar |
E807168
|
entity |
| Predicate | successorAsGovernorOfKhurasan |
P198881
|
FINISHED |
| Object | Abu Muslim al-Khurasani |
—
|
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: Abu Muslim al-Khurasani | Statement: [Nasr ibn Sayyar, successorAsGovernorOfKhurasan, Abu Muslim al-Khurasani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsGovernorOfKhurasan Context triple: [Nasr ibn Sayyar, successorAsGovernorOfKhurasan, Abu Muslim al-Khurasani]
-
A.
predecessorAsGovernorOfKhurasan
Indicates that one person previously held the position of governor of Khurasan before another person.
-
B.
successorAsSatrapOfBactria
Indicates that one entity became the next satrap (provincial governor) of Bactria after another entity.
-
C.
predecessorAsRulerOfKandahar
Indicates that one entity previously held the position of ruler of Kandahar immediately before another entity.
-
D.
successorAsGovernorOfDamascus
Indicates that one person became the next governor of Damascus after another person.
-
E.
successorAsShah
Indicates that one entity became the next Shah (ruler) following another entity in succession.
- F. None of above. chosen
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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: April 30, 2026, 10:45 p.m.