Triple
T8423003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banbury (UK Parliament constituency) |
E198906
|
entity |
| Predicate | currentMPStartDate |
P69740
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Banbury (UK Parliament constituency), currentMPStartDate, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMPStartDate Context triple: [Banbury (UK Parliament constituency), currentMPStartDate, 2015]
-
A.
earlierMPStartDate
Indicates that one entity’s MP start date occurs earlier in time than another entity’s MP start date.
-
B.
currentMP
chosen
Indicates that the subject is the person who currently serves as a Member of Parliament representing the object’s constituency or jurisdiction.
-
C.
previousMPStartYear
Indicates the year in which the subject’s immediately preceding term as a Member of Parliament began.
-
D.
candidacyStartDate
Indicates the date on which an entity’s candidacy for a role, position, or election officially begins.
-
E.
currentChairStartDate
Indicates the date on which the person’s current term as chair officially began.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859f787481908a11797a317c8849 |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.