Triple
T9126750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Myanmar general election |
E218983
|
entity |
| Predicate | typeOfTransition |
P36477
|
FINISHED |
| Object | military-managed democratization |
—
|
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: military-managed democratization | Statement: [2010 Myanmar general election, typeOfTransition, military-managed democratization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTransition Context triple: [2010 Myanmar general election, typeOfTransition, military-managed democratization]
-
A.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
typeOfTranslation
Indicates that one entity is a specific kind or category of translation in relation to another entity.
-
C.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
D.
dstTransitionRuleType
Indicates the type or category of rule that governs how a system transitions into or out of daylight saving time.
-
E.
turnoverType
Indicates the specific category or nature of a turnover event, such as how or why control of an asset, position, or role changes from one party to another.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8c93d3c8190b003b2b1af2003b2 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.