Triple
T2850874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Pugo |
E63087
|
entity |
| Predicate | facedConsequencesFrom |
P812
|
FINISHED |
| Object | failure of the August 1991 coup attempt |
—
|
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: failure of the August 1991 coup attempt | Statement: [Boris Pugo, facedConsequencesFrom, failure of the August 1991 coup attempt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedConsequencesFrom Context triple: [Boris Pugo, facedConsequencesFrom, failure of the August 1991 coup attempt]
-
A.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
violationConsequences
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
C.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
D.
consequenceOfRevocation
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
E.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf437328819098506ec8a3a23e11 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.