Triple
T17792924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Malik al-Zahir Baibars |
E444212
|
entity |
| Predicate | roleInBattleOfAinJalut |
P24445
|
FINISHED |
| Object | commander |
—
|
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: commander | Statement: [al-Malik al-Zahir Baibars, roleInBattleOfAinJalut, commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfAinJalut Context triple: [al-Malik al-Zahir Baibars, roleInBattleOfAinJalut, commander]
-
A.
MamlukCommander
chosen
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
B.
roleAtMongolCourt
Indicates a person's specific position, function, or status within the Mongol imperial court.
-
C.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
D.
AbbasidCommander
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
E.
sideInBattleOfHunayn
Indicates that an entity participated as a side (party or faction) in the Battle of Hunayn.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879859408190875835bd255e1185 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.