Triple
T29826561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 Myanmar by-elections |
E757395
|
entity |
| Predicate | seatShareOfNLD |
P168688
|
FINISHED |
| Object | majority of contested seats |
—
|
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: majority of contested seats | Statement: [2012 Myanmar by-elections, seatShareOfNLD, majority of contested seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatShareOfNLD Context triple: [2012 Myanmar by-elections, seatShareOfNLD, majority of contested seats]
-
A.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
B.
sharesRankWith
Indicates that two entities have the same rank or hierarchical level within a given ordering or classification.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesCountryWith
Indicates that two entities are located in, originate from, or are otherwise associated with the same country.
-
E.
hasAudienceShareRank
Indicates the relative position or ranking of an entity based on the size or proportion of its audience share compared to others.
- F. None of above. chosen
Provenance (4 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_69f67598dff081908ff0ec79a48b55ec |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 5:32 p.m.