Triple
T27742267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 South African general election |
E701884
|
entity |
| Predicate | FreedomFrontPlusSeats |
P163541
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [2014 South African general election, FreedomFrontPlusSeats, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FreedomFrontPlusSeats Context triple: [2014 South African general election, FreedomFrontPlusSeats, 4]
-
A.
IFPSeats
Indicates that an entity has a specified number or configuration of seats in an International First/Front/Flight Passenger (IFP) seating context.
-
B.
EFFSeats
Indicates a relationship where a person or entity holds or occupies a seat or position within an organization, body, or context.
-
C.
ANCSeats
Indicates the number of seats held or allocated to the ANC (African National Congress) in a representative body such as a parliament or council.
-
D.
DASeats
Indicates that an entity assigns or provides seating arrangements for another entity or group.
-
E.
PPSeats
Indicates that an entity provides or contains seats, typically specifying the seating capacity or arrangement associated with it.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 4:12 p.m.