Triple
T9126732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Myanmar general election |
E218983
|
entity |
| Predicate | upperHouseSeats |
P48166
|
FINISHED |
| Object | 168 elected 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: 168 elected seats | Statement: [2010 Myanmar general election, upperHouseSeats, 168 elected seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperHouseSeats Context triple: [2010 Myanmar general election, upperHouseSeats, 168 elected seats]
-
A.
numberOfMembersUpperHouse
Indicates the total count of individuals serving as members in the upper house of a legislative body.
-
B.
numberOfSeatsInSenate
chosen
Indicates the total count of seats allocated in a given senate.
-
C.
upperHouseRepresentation
Indicates the relationship by which an entity is represented in, or holds seats within, an upper legislative chamber (such as a senate or upper house of parliament).
-
D.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
-
E.
upperHouseCounterpart
Indicates that one legislative body is the corresponding or equivalent chamber in the upper house relative to another body.
- 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.