Triple
T6423671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesham and Amersham (UK Parliament constituency) |
E128004
|
entity |
| Predicate | previousMPStartDate |
P19035
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Chesham and Amersham (UK Parliament constituency), previousMPStartDate, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMPStartDate Context triple: [Chesham and Amersham (UK Parliament constituency), previousMPStartDate, 1992]
-
A.
previousMP
Indicates that one entity served as a Member of Parliament for a given constituency or position immediately before another specified entity.
-
B.
previousHolderStartDate
chosen
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
-
C.
preByElectionMPTenureStart
Indicates the start date of a member of parliament’s tenure that began before a by-election.
-
D.
candidacyStartDate
Indicates the date on which an entity’s candidacy for a role, position, or election officially begins.
-
E.
previewStartDate
Indicates the date and time when a preview period for something begins.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.