Triple
T11801588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Bexley and Sidcup |
E280637
|
entity |
| Predicate | reasonFor2021ByElection |
P14472
|
FINISHED |
| Object | death of James Brokenshire |
—
|
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: death of James Brokenshire | Statement: [Old Bexley and Sidcup, reasonFor2021ByElection, death of James Brokenshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonFor2021ByElection Context triple: [Old Bexley and Sidcup, reasonFor2021ByElection, death of James Brokenshire]
-
A.
reasonForEarlyElection
Indicates that one event, condition, or circumstance serves as the cause or justification for an early election being held.
-
B.
byElectionReason
chosen
Indicates the reason or cause for which a by-election is being held.
-
C.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
D.
electoralPurpose
Indicates that something is intended, designed, or used for the purposes of an election or electoral process.
-
E.
nextElectionDeterminedBy
Indicates that the outcome or occurrence of the next election is decided or governed by a specified factor, rule, event, or entity.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.