Triple
T7845588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African general elections |
E181914
|
entity |
| Predicate | lowerHouseSeatsElected |
P51739
|
FINISHED |
| Object | 400 |
—
|
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: 400 | Statement: [South African general elections, lowerHouseSeatsElected, 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerHouseSeatsElected Context triple: [South African general elections, lowerHouseSeatsElected, 400]
-
A.
hasLowerHouseSeats
chosen
Indicates the number of seats an entity holds in the lower house of a bicameral legislature.
-
B.
lowerHouseElectedBy
Indicates that the members of the lower house of a legislature are chosen through a specified method or by a particular group of voters or body.
-
C.
lowerHouseComposition
Indicates the makeup or distribution of seats among parties or groups within the lower house of a legislature.
-
D.
lowerHouseComposedOf
Indicates that a lower legislative house is made up of, or constituted by, specific members, parties, or organizational units.
-
E.
lowerHouse
Indicates that one entity functions as the lower chamber of a bicameral legislature in relation to a given political body or system.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163d92fc8190a4efcb08d6b3d404 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.