Triple
T34316692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abd Allah ibn Hanzala |
E880603
|
entity |
| Predicate | roleInBattleOfAlHarrah |
P202833
|
FINISHED |
| Object | commander of Medinan forces |
—
|
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 of Medinan forces | Statement: [Abd Allah ibn Hanzala, roleInBattleOfAlHarrah, commander of Medinan forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfAlHarrah Context triple: [Abd Allah ibn Hanzala, roleInBattleOfAlHarrah, commander of Medinan forces]
-
A.
roleInBattleOfMuʾtah
Indicates the specific role or involvement an entity had in the Battle of Muʾtah.
-
B.
sideInBattleOfMarjRahit
Indicates that an entity participated as a side or faction in the Battle of Marj Rahit.
-
C.
sideInBattleOfHunayn
Indicates that an entity participated as a side (party or faction) in the Battle of Hunayn.
-
D.
AbbasidCommander
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
E.
roleDuringCrusades
Indicates the specific function, position, or involvement an entity had in relation to the Crusades during the period they occurred.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_6a00c3355498819088253d5e5c17267f |
completed | May 10, 2026, 5:41 p.m. |
Created at: May 1, 2026, 1:57 a.m.