Triple
T21190815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussein Badreddin al-Houthi |
E522205
|
entity |
| Predicate | movementAfterDeath |
P143225
|
FINISHED |
| Object | Houthi movement led by Abdul-Malik al-Houthi |
—
|
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: Houthi movement led by Abdul-Malik al-Houthi | Statement: [Hussein Badreddin al-Houthi, movementAfterDeath, Houthi movement led by Abdul-Malik al-Houthi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementAfterDeath Context triple: [Hussein Badreddin al-Houthi, movementAfterDeath, Houthi movement led by Abdul-Malik al-Houthi]
-
A.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
B.
positionOnDeath
Indicates the role, title, or position an entity held at the time of its death.
-
C.
bodyLocationAfterDeath
Indicates the location or position of an entity’s body after its death.
-
D.
completionAfterDeathOf
Indicates that one event, process, or work is completed only after the death of a specified person.
-
E.
successorStateAfterDeath
Indicates the resulting state or condition that follows an entity’s death.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:07 p.m.