Triple
T11163630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwean general election, 2005 |
E264103
|
entity |
| Predicate | additionalNonElectedParliamentarySeats |
P98186
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Zimbabwean general election, 2005, additionalNonElectedParliamentarySeats, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalNonElectedParliamentarySeats Context triple: [Zimbabwean general election, 2005, additionalNonElectedParliamentarySeats, 30]
-
A.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
B.
providesReservedParliamentarySeatsFor
Indicates that one entity allocates or guarantees a specific number of parliamentary seats exclusively for another entity.
-
C.
parliamentarySeatsTotal
Indicates the total number of seats in a given parliament or parliamentary body.
-
D.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
E.
numberOfAtLargeSeats
Indicates the total count of at-large seats (positions not tied to specific districts or subunits) associated with an entity.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8832fe88190a74d81f9ed547baa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.