Triple
T920504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Winter |
E19871
|
entity |
| Predicate | describesOutcomeOf |
P22390
|
FINISHED |
| Object | 2011 Arab uprisings |
—
|
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: 2011 Arab uprisings | Statement: [Arab Winter, describesOutcomeOf, 2011 Arab uprisings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesOutcomeOf Context triple: [Arab Winter, describesOutcomeOf, 2011 Arab uprisings]
-
A.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
C.
subsequentOutcomeForWinner
Indicates that the predicate links a winner to an outcome or event that occurs to or for them after their initial victory.
-
D.
supportsOutcome
Indicates that one entity contributes to enabling, sustaining, or improving the achievement of a particular outcome associated with another entity.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.