Triple
T34474496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Baghdad (812–813) |
E884991
|
entity |
| Predicate | notableCommanderSideAl-Ma'mun |
P95827
|
FINISHED |
| Object | Tahir ibn al-Husayn |
E890789
|
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: Tahir ibn al-Husayn | Statement: [Siege of Baghdad (812–813), notableCommanderSideAl-Ma'mun, Tahir ibn al-Husayn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderSideAl-Ma'mun Context triple: [Siege of Baghdad (812–813), notableCommanderSideAl-Ma'mun, Tahir ibn al-Husayn]
-
A.
AbbasidCommander
chosen
Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
-
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 a relationship where one entity is the owner or possessor of another entity.
-
D.
ArabCommander
Indicates that the subject serves as a military commander associated with Arab forces or entities.
-
E.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
- F. None of above.
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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3740f7b8608190b1f066dccfb550e6 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.