Triple
T15295001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Helens South and Whiston (UK Parliament constituency) |
E365631
|
entity |
| Predicate | previousMpTermEnd |
P100319
|
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: [St Helens South and Whiston (UK Parliament constituency), previousMpTermEnd, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMpTermEnd Context triple: [St Helens South and Whiston (UK Parliament constituency), previousMpTermEnd, 2015]
-
A.
previousMP
Indicates that one entity served as a Member of Parliament for a given constituency or position immediately before another specified entity.
-
B.
previousPostEndDate
chosen
Indicates the date on which the immediately preceding post, position, or assignment ended.
-
C.
previousTermLengthChangedIn
Indicates that the duration or length of the immediately preceding term has been modified within a specified context or period.
-
D.
nextTermStartDate
Indicates the date on which the next term or period in a sequence is scheduled to begin.
-
E.
termAsMPEnd
Indicates that something is designated or used as the end point of a measurement period (MP).
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e036848c1881908fbaaae0216d6d27 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.