Triple
T11288520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh South |
E267260
|
entity |
| Predicate | electionResult2010 |
P98309
|
FINISHED |
| Object | Labour hold |
—
|
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: Labour hold | Statement: [Edinburgh South, electionResult2010, Labour hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionResult2010 Context triple: [Edinburgh South, electionResult2010, Labour hold]
-
A.
electoralVoteOutcome
Indicates the result of an election in terms of how electoral votes are allocated or distributed among candidates or options.
-
B.
republicanPopularVoteShare
Indicates the proportion of total votes in an election that were cast for the Republican Party.
-
C.
resultIn2002Election
Indicates the outcome or consequence that occurred specifically in relation to the 2002 election.
-
D.
presidentialVote
Indicates that an entity casts or records a vote in a presidential election for a particular candidate or option.
-
E.
electionContests
Indicates that one election is in competition with, or formally challenges the outcome or validity of, another election.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98875a08190b8509fe55e49d52d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.