Triple
T38282511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husayn ibn Ali |
E1022114
|
entity |
| Predicate | armyOpposed |
P138442
|
FINISHED |
| Object | Umayyad forces at Karbala |
—
|
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: Umayyad forces at Karbala | Statement: [Husayn ibn Ali, armyOpposed, Umayyad forces at Karbala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armyOpposed Context triple: [Husayn ibn Ali, armyOpposed, Umayyad forces at Karbala]
-
A.
opposingUnits
chosen
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within a given context.
-
B.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
C.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
-
D.
opposedByMilitaryForce
Indicates that one party’s actions, plans, or presence are actively resisted or countered through the use or threat of military force by another party.
-
E.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.