Triple
T15489674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldham East and Saddleworth |
E377145
|
entity |
| Predicate | hasPost1997Status |
P116664
|
FINISHED |
| Object | continuing constituency since 1997 boundary changes |
—
|
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: continuing constituency since 1997 boundary changes | Statement: [Oldham East and Saddleworth, hasPost1997Status, continuing constituency since 1997 boundary changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPost1997Status Context triple: [Oldham East and Saddleworth, hasPost1997Status, continuing constituency since 1997 boundary changes]
-
A.
statusAfter1997
chosen
Indicates the status or condition of an entity specifically in the period after the year 1997.
-
B.
post1967Status
Indicates the status or condition of an entity specifically in the period after the year 1967.
-
C.
statusAfter1799
Indicates the condition or state of something as it existed after the year 1799.
-
D.
statusAfter1995
Indicates the condition or state of an entity specifically in the period after the year 1995.
-
E.
statusAfter1970
Indicates the status or condition of an entity as it exists after the year 1970.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faaca588190b0397bc2e27a522a |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:48 a.m.