Triple
T31318852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Win Myint |
E798669
|
entity |
| Predicate | wasOustedIn |
P22775
|
FINISHED |
| Object | 2021 Myanmar military coup d’état |
—
|
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: 2021 Myanmar military coup d’état | Statement: [Win Myint, wasOustedIn, 2021 Myanmar military coup d’état]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOustedIn Context triple: [Win Myint, wasOustedIn, 2021 Myanmar military coup d’état]
-
A.
wasDeposedAt
Indicates that an entity lost its position, power, or office through deposition at a specific time or event.
-
B.
wasSackedBy
Indicates that one entity was dismissed or fired from a position or role by another entity.
-
C.
deposedFrom
Indicates that an entity has been removed from a position of power, authority, or office, typically by force or formal action.
-
D.
overthrownIn
chosen
Indicates that one entity (such as a government, leader, or regime) was removed from power or defeated in a specific event, context, or time period represented by the other entity.
-
E.
wasToppled
Indicates that an entity was forcibly overthrown, removed from power, or knocked down from its previous position or status.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69eab7980819083ab0ee519699561 |
completed | May 3, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.