Triple
T15117811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Midlands mayoral election, 2017 |
E361086
|
entity |
| Predicate | votesCast |
P8455
|
FINISHED |
| Object | approximately 505000 |
—
|
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: approximately 505000 | Statement: [West Midlands mayoral election, 2017, votesCast, approximately 505000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votesCast Context triple: [West Midlands mayoral election, 2017, votesCast, approximately 505000]
-
A.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
B.
votesOnly
Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
-
C.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
D.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
-
E.
totalVotesCast
chosen
Indicates the total number of votes that have been cast in a given election or voting event.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.