Triple
T27979595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Carswell |
E706581
|
entity |
| Predicate | byElectionWon |
P122073
|
FINISHED |
| Object | Clacton by-election, 2014 |
—
|
NE NERFINISHED |
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: Clacton by-election, 2014 | Statement: [Douglas Carswell, byElectionWon, Clacton by-election, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: byElectionWon Context triple: [Douglas Carswell, byElectionWon, Clacton by-election, 2014]
-
A.
electedCandidate
Indicates that a particular person has been chosen as the winner in an election for a given position or office.
-
B.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
-
C.
electionWinner
chosen
Indicates that the subject is the candidate who received the highest support and officially won a particular election.
-
D.
wonParliamentaryElection
Indicates that one party or candidate achieved victory in a parliamentary election over others.
-
E.
chairElectedBy
Indicates that a person holds the position of chair as a result of being elected by another person or group.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b6802d081908721f6bb9c0d8180 |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:43 p.m.