Triple
T35708048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayyubid–Crusader conflicts |
E1031770
|
entity |
| Predicate | notableAyyubidLeader |
P207105
|
FINISHED |
| Object | al-Adil I |
E392732
|
NE 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: al-Adil I | Statement: [Ayyubid–Crusader conflicts, notableAyyubidLeader, al-Adil I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAyyubidLeader Context triple: [Ayyubid–Crusader conflicts, notableAyyubidLeader, al-Adil I]
-
A.
المالك
Indicates a relationship where one entity is the owner or possessor of another entity.
-
B.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
C.
إسهام
Indicates contributing or participating in bringing about, supporting, or advancing something, often as one factor among others.
-
D.
AbbasidCommander
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
E.
associatedEmperorDuringFirstCrusade
Indicates a relationship where an entity is linked to the emperor who held authority or was prominently involved during the time of the First Crusade.
- F. None of above. chosen
Provenance (5 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885e79e788190add7887e2fefb7c7 |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.