Triple
T33335190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston and Skegness |
E853514
|
entity |
| Predicate | referendumVoteLeaveShare |
P8661
|
FINISHED |
| Object | over 75% |
—
|
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: over 75% | Statement: [Boston and Skegness, referendumVoteLeaveShare, over 75%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referendumVoteLeaveShare Context triple: [Boston and Skegness, referendumVoteLeaveShare, over 75%]
-
A.
votedLeaveOrRemain
Indicates that an entity participated in a vote on a leave-or-remain decision and specifies which of the two options they chose.
-
B.
referendumResultLeavePercentage
chosen
Indicates the percentage of votes in a referendum that were cast in favor of the "leave" option.
-
C.
independenceReferendum
Indicates a formal vote in which a population decides whether a territory or region should become politically independent from its current governing state or authority.
-
D.
referendumRelated
Indicates a relationship where something is connected to, associated with, or arising from a referendum process or its outcomes.
-
E.
subjectOfReferendum
Indicates that something is the issue, proposal, or matter being decided upon in a referendum.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 1:34 a.m.