Triple
T29826511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1990 Myanmar general election |
E757394
|
entity |
| Predicate | resultRecognizedByJunta |
P15661
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [1990 Myanmar general election, resultRecognizedByJunta, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultRecognizedByJunta Context triple: [1990 Myanmar general election, resultRecognizedByJunta, no]
-
A.
resolutionCarriedOutBy
Indicates that the execution or implementation of a resolution is performed by a specified agent or entity.
-
B.
resultRecognizedBy
chosen
Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
-
C.
judicialFinding
Indicates a formal determination or conclusion reached by a judicial authority regarding facts, law, or liability in a legal matter.
-
D.
recognizedAsOrdinanceBy
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
-
E.
decidedUnder
Indicates that a decision or outcome is made within the authority, rules, or jurisdiction of a particular entity or context.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 5:32 p.m.