Triple
T10876519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwean general election, 2013 |
E256812
|
entity |
| Predicate | parliamentarySeatsTotal |
P96187
|
FINISHED |
| Object | 270 |
—
|
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: 270 | Statement: [Zimbabwean general election, 2013, parliamentarySeatsTotal, 270]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarySeatsTotal Context triple: [Zimbabwean general election, 2013, parliamentarySeatsTotal, 270]
-
A.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
B.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
C.
numberOfSeatsWon
Indicates the quantity of seats secured by an entity (such as a party or candidate) in an election or representative body.
-
D.
governingBodySeats
Indicates the number of seats or positions an entity holds in a specified governing body.
-
E.
electoralRegionSeatCount
Indicates the number of seats allocated to a given electoral region within a representative body or legislature.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ac901881909938cabe4d21bdbf |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.