Triple
T16735503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adud al-Dawla |
E406705
|
entity |
| Predicate | relationshipToCaliph |
P17619
|
FINISHED |
| Object | nominally recognized Abbasid caliphs |
—
|
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: nominally recognized Abbasid caliphs | Statement: [Adud al-Dawla, relationshipToCaliph, nominally recognized Abbasid caliphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCaliph Context triple: [Adud al-Dawla, relationshipToCaliph, nominally recognized Abbasid caliphs]
-
A.
associatedCaliph
chosen
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
B.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
C.
positionRelativeToCaliph
Indicates the spatial or hierarchical position an entity holds in relation to the caliph.
-
D.
relationToUthman
Indicates the type of relationship or connection an entity has to Uthman.
-
E.
servedCaliph
Indicates that one entity acted in service to, or under the authority of, a caliph.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c39c570819088723d59242c5c5c |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.