Triple
T35762434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mansur Nasir al-Din Muhammad |
E1033912
|
entity |
| Predicate | followsDynastyFoundedBy |
P199077
|
FINISHED |
| Object | Saladin |
—
|
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: Saladin | Statement: [Al-Mansur Nasir al-Din Muhammad, followsDynastyFoundedBy, Saladin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsDynastyFoundedBy Context triple: [Al-Mansur Nasir al-Din Muhammad, followsDynastyFoundedBy, Saladin]
-
A.
successorStateToDynastyFounded
Indicates that one state is the political successor to a dynasty that originally founded or established it.
-
B.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
C.
dynastyFoundedByOffspring
Indicates that a dynasty was established by the offspring (child or descendant) of a particular person or entity.
-
D.
branchOfDynastyFounded
Indicates that one dynasty is a branch or offshoot of another, earlier-founded dynasty.
-
E.
followsDynasty
Indicates that one dynasty succeeds or comes after another in a historical or genealogical sequence.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:06 p.m.