Triple
T36338580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudanese Islamist movement |
E894851
|
entity |
| Predicate | facedSetback |
P117819
|
FINISHED |
| Object | 2018–2019 Sudanese revolution |
—
|
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: 2018–2019 Sudanese revolution | Statement: [Sudanese Islamist movement, facedSetback, 2018–2019 Sudanese revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedSetback Context triple: [Sudanese Islamist movement, facedSetback, 2018–2019 Sudanese revolution]
-
A.
sufferedSetback
chosen
Indicates that an entity has experienced a negative event or obstacle that hindered its progress or success.
-
B.
hasSetbackDesign
Indicates that one entity incorporates a design feature that sets it back or away from another reference line, boundary, or structure.
-
C.
failed
Indicates that an attempted action or process did not succeed in achieving its intended outcome.
-
D.
fellWith
Indicates that one entity fell at the same time as, or in conjunction with, another entity.
-
E.
experiencedFailure
Indicates that an entity has undergone or encountered a failure in performing an action, achieving a goal, or maintaining a desired state.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.