Triple
T9422519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazid I |
E227189
|
entity |
| Predicate | orderedCampaign |
P79122
|
FINISHED |
| Object | expedition against Husayn ibn Ali |
—
|
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: expedition against Husayn ibn Ali | Statement: [Yazid I, orderedCampaign, expedition against Husayn ibn Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedCampaign Context triple: [Yazid I, orderedCampaign, expedition against Husayn ibn Ali]
-
A.
orderedEvent
Indicates that one event occurs before another in a defined temporal or logical sequence.
-
B.
sponsoringOrder
Indicates that one entity provides sponsorship or financial backing for another entity’s order or purchase.
-
C.
openedCampaign
chosen
Indicates that an entity has initiated or launched a campaign, transitioning it from a non-active to an active or publicly accessible state.
-
D.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
E.
orderGroup
Indicates that multiple individual orders are associated together as a single grouped order entity or batch.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c27c8cc8190a11162c10c33b17e |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.