Triple
T30546353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad ibn Abd Allah |
E777427
|
entity |
| Predicate | successorThroughOffspring |
P27930
|
FINISHED |
| Object | Abd al-Rahman III |
—
|
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: Abd al-Rahman III | Statement: [Muhammad ibn Abd Allah, successorThroughOffspring, Abd al-Rahman III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorThroughOffspring Context triple: [Muhammad ibn Abd Allah, successorThroughOffspring, Abd al-Rahman III]
-
A.
successorOfFather
Indicates that one entity is the successor or heir of another entity’s father.
-
B.
successorInLineage
chosen
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
C.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
D.
resultedInSuccessionFrom
Indicates that one entity’s outcome or event directly caused or led to the succession or replacement of another entity.
-
E.
successorFoundedBy
Indicates that an entity was founded by the successor of another specified 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 29, 2026, 8:19 p.m.