Triple
T15277232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stretford and Urmston |
E365173
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Flixton |
E297644
|
NE 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: Flixton | Statement: [Stretford and Urmston, contains, Flixton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flixton Context triple: [Stretford and Urmston, contains, Flixton]
-
A.
Flixton
Flixton is a small village and civil parish in Suffolk, England, known for its rural character and historic setting.
-
B.
Flixton
chosen
Flixton is a suburban area in the Metropolitan Borough of Trafford, Greater Manchester, England, known primarily as a residential community.
-
C.
Euxton
Euxton is a village and civil parish in Lancashire, England, situated near the town of Leyland.
-
D.
Fletton
Fletton is a suburban area of Peterborough in Cambridgeshire, England, historically known for its brickworks and residential development.
-
E.
Fritchley
Fritchley is a small village in Derbyshire, England, known for its rural character and proximity to the larger village of Crich.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e00953bc848190b83919f39d5ee37b |
completed | April 15, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef734f488190951d029183d456f5 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:14 a.m.