Triple
T33932006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | يزيد بن معاوية |
E869920
|
entity |
| Predicate | أبرز الأحداث في عهده |
P160798
|
FINISHED |
| Object | واقعة كربلاء |
—
|
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: واقعة كربلاء | Statement: [يزيد بن معاوية, أبرز الأحداث في عهده, واقعة كربلاء]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: أبرز الأحداث في عهده Context triple: [يزيد بن معاوية, أبرز الأحداث في عهده, واقعة كربلاء]
-
A.
notableEventDuringTerm
Indicates that a significant or noteworthy event occurred during the time span of a particular term in office or period of service.
-
B.
شهد عهده
chosen
Indicates that something occurred, developed, or took place during the period of someone’s rule, leadership, or tenure.
-
C.
notableEventInCareer
Indicates that a particular event is a significant or defining occurrence within an entity’s professional career.
-
D.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
E.
riseToPowerDuringReignOf
Indicates that one entity attained political or authoritative power while another entity was ruling or holding sovereign authority.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.