Triple
T4607676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Representatives of Yemen |
E100476
|
entity |
| Predicate | electionPostponementsReason |
P18029
|
FINISHED |
| Object | political instability |
—
|
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: political instability | Statement: [House of Representatives of Yemen, electionPostponementsReason, political instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionPostponementsReason Context triple: [House of Representatives of Yemen, electionPostponementsReason, political instability]
-
A.
byElectionReason
Indicates the reason or cause for which a by-election is being held.
-
B.
postponementReason
chosen
Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
-
C.
2018PostponementReason
Indicates the reason why an event, action, or decision scheduled for 2018 was postponed.
-
D.
reasonForEventualRatification
Indicates the underlying cause or justification that led to the eventual ratification of something (such as a treaty, agreement, or decision).
-
E.
losesElectionFor
Indicates that one candidate is defeated by another candidate in a specific election for a particular office or position.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599debdc81909d11d0e871c666bb |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.