Triple
T31631211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasr ibn Sayyar |
E807168
|
entity |
| Predicate | governorUnderCaliph |
P95828
|
FINISHED |
| Object | Hisham ibn Abd al-Malik |
—
|
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: Hisham ibn Abd al-Malik | Statement: [Nasr ibn Sayyar, governorUnderCaliph, Hisham ibn Abd al-Malik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorUnderCaliph Context triple: [Nasr ibn Sayyar, governorUnderCaliph, Hisham ibn Abd al-Malik]
-
A.
servedCaliph
chosen
Indicates that one entity acted in service to, or under the authority of, a caliph.
-
B.
primaryCaliph
Indicates that one entity serves as the main or first-recognized caliph (successor/leader) in relation to another entity.
-
C.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
D.
politicalRoleBeforeCaliphate
Indicates that an entity held a specific political position or role prior to the establishment or assumption of the caliphate.
-
E.
secondCaliph
Indicates that the subject is the second individual to hold the position or title of caliph in a given succession.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: April 30, 2026, 10:45 p.m.