Triple
T30519559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Nasir li-Din Allah |
E776656
|
entity |
| Predicate | linkedRulerDynasty |
P72201
|
FINISHED |
| Object | Umayyad |
—
|
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: Umayyad | Statement: [al-Nasir li-Din Allah, linkedRulerDynasty, Umayyad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerDynasty Context triple: [al-Nasir li-Din Allah, linkedRulerDynasty, Umayyad]
-
A.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
B.
rulingDynasties
Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
-
C.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
D.
reignInDynasty
chosen
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
E.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 29, 2026, 8:17 p.m.