Triple
T35045232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Poson |
E1011177
|
entity |
| Predicate | commanderOfAbbasidForces |
P95827
|
FINISHED |
| Object | Umar al-Aqta |
—
|
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: Umar al-Aqta | Statement: [Battle of Poson, commanderOfAbbasidForces, Umar al-Aqta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderOfAbbasidForces Context triple: [Battle of Poson, commanderOfAbbasidForces, Umar al-Aqta]
-
A.
AbbasidCommander
chosen
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
B.
ArabCommander
Indicates that the subject serves as a military commander associated with Arab forces or entities.
-
C.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
D.
IraqiCommander
Indicates a relationship where an individual serves in the role of a military commander for Iraqi armed or security forces.
-
E.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:01 p.m.