Triple
T23855084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton Keynes North |
E592281
|
entity |
| Predicate | hasPost-2010Status |
P86249
|
FINISHED |
| Object | successor to North East Milton Keynes constituency |
—
|
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: successor to North East Milton Keynes constituency | Statement: [Milton Keynes North, hasPost-2010Status, successor to North East Milton Keynes constituency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPost-2010Status Context triple: [Milton Keynes North, hasPost-2010Status, successor to North East Milton Keynes constituency]
-
A.
statusAfter2010
Indicates the condition or state of an entity specifically in the period after the year 2010.
-
B.
statusBefore2010s
Indicates that the status or condition of an entity is evaluated or defined as it was prior to the 2010s.
-
C.
post2000Status
Indicates whether a given entity’s status, condition, or classification applies specifically to the period after the year 2000.
-
D.
post2009Status
chosen
Indicates the status or condition of an entity specifically in the period after the year 2009.
-
E.
statusAfter2011
Indicates the condition or state of an entity specifically in the period following the year 2011.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.