Triple
T1602191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chat Moss |
E34417
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Worsley |
E44025
|
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: Worsley | Statement: [Chat Moss, near, Worsley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Worsley Context triple: [Chat Moss, near, Worsley]
-
A.
Worsley
chosen
Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
-
B.
Urmston
Urmston is a suburban town in Greater Manchester, England, known primarily as a residential area within the Metropolitan Borough of Trafford.
-
C.
Droylsden
Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
-
D.
Wythenshawe
Wythenshawe is a large suburban area in south Manchester, England, known for its extensive housing estates, green spaces, and proximity to Manchester Airport.
-
E.
Ordsall
Ordsall is an inner-city district of Salford in Greater Manchester, England, known for its historic Ordsall Hall and proximity to Manchester city centre.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62292d1c819080b597199dc6b8d5 |
completed | March 6, 2026, 5:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad608dfc688190a81a502c810f67fb |
completed | March 8, 2026, 11:42 a.m. |
Created at: March 4, 2026, 7:28 p.m.