Triple
T4448550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyne |
E96348
|
entity |
| Predicate | hasByElection |
P47256
|
FINISHED |
| Object | 2008 Lyne by-election |
—
|
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: 2008 Lyne by-election | Statement: [Lyne, hasByElection, 2008 Lyne by-election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasByElection Context triple: [Lyne, hasByElection, 2008 Lyne by-election]
-
A.
hasByElections
chosen
Indicates that one entity conducts, experiences, or is associated with one or more by-elections in relation to another contextual entity (such as a jurisdiction, office, or time period).
-
B.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
-
C.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
D.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
E.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d45b748190b09b7067fc6279b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.