Triple
T27742261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 South African general election |
E701884
|
entity |
| Predicate | COPESeats |
P163189
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [2014 South African general election, COPESeats, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: COPESeats Context triple: [2014 South African general election, COPESeats, 3]
-
A.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
B.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
-
C.
secondPartySeats
Indicates that a second party assigns or provides seating or seats to another entity.
-
D.
seatOrDomain
Indicates a relationship where something serves as, or is associated with, the primary location, base, or jurisdictional area (seat or domain) of an entity.
-
E.
multiSeat
Indicates that an entity is designed to accommodate or provide seating for multiple individuals simultaneously.
- 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_69f63717b8c48190abd8ebcc54c76c46 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:12 p.m.