Triple
T28174274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 United Kingdom European Union membership referendum |
E715546
|
entity |
| Predicate | votesForLeave |
P8661
|
FINISHED |
| Object | 17410742 |
—
|
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: 17410742 | Statement: [2016 United Kingdom European Union membership referendum, votesForLeave, 17410742]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votesForLeave Context triple: [2016 United Kingdom European Union membership referendum, votesForLeave, 17410742]
-
A.
referendumResultLeavePercentage
chosen
Indicates the percentage of votes in a referendum that were cast in favor of the "leave" option.
-
B.
referendumYesPercentage
Indicates the percentage of votes cast in favor of the "yes" option in a referendum.
-
C.
referendumSupportNorthernIreland
Indicates support for holding or backing the outcome of a referendum specifically concerning Northern Ireland.
-
D.
votesForChange
Indicates that an entity expresses support for or chooses an option aimed at altering an existing state, policy, or condition.
-
E.
numberOfVotesLabour
Indicates the total count of votes that were cast for the Labour party in a given election or voting context.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:15 p.m.