Triple
T30630881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Burmese coup d'état |
E779708
|
entity |
| Predicate | newRegime |
P151359
|
FINISHED |
| Object | Revolutionary Council of Burma |
—
|
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: Revolutionary Council of Burma | Statement: [1962 Burmese coup d'état, newRegime, Revolutionary Council of Burma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newRegime Context triple: [1962 Burmese coup d'état, newRegime, Revolutionary Council of Burma]
-
A.
replacedRegime
Indicates that one regime has been supplanted and taken over by another regime.
-
B.
createdRegimeOf
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for another entity.
-
C.
replacesRegime
Indicates that one governing regime is superseded and taken over by another.
-
D.
useRegime
Indicates a relationship where a particular method, system, or set of rules is applied or followed in carrying out an action or process.
-
E.
replacedRegimeOf
chosen
Indicates that one regime has taken the place of or succeeded another regime in power or authority.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1d060c81908a5a9524876f04ed |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.