Triple
T10952766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omar al-Bashir |
E258764
|
entity |
| Predicate | reasonForOuster |
P41278
|
FINISHED |
| Object | mass protests |
—
|
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: mass protests | Statement: [Omar al-Bashir, reasonForOuster, mass protests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForOuster Context triple: [Omar al-Bashir, reasonForOuster, mass protests]
-
A.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
-
B.
reasonForRenunciation
Indicates the specific cause, motive, or circumstance that led an entity to renounce or give up something.
-
C.
reasonForDismissal
chosen
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
D.
reasonForStrike
Indicates the cause or justification behind a strike action.
-
E.
reasonForExcommunication
Indicates the specific cause or grounds that led to an entity’s excommunication.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fcfb3c8190b7823869670184a6 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.