Triple
T31265599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAC |
E797244
|
entity |
| Predicate | crackedDownOn |
P171520
|
FINISHED |
| Object | anti-coup 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: anti-coup protests | Statement: [SAC, crackedDownOn, anti-coup protests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crackedDownOn Context triple: [SAC, crackedDownOn, anti-coup protests]
-
A.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
B.
stoodDown
Indicates that an entity relinquished its active role, position, or state of readiness, often stepping aside from duty or responsibility.
-
C.
brokenOn
Indicates that an object or system ceased functioning or became damaged at a specific time or on a specific date.
-
D.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
E.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:12 p.m.