Triple
T4178712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde |
E86540
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Tameside |
E29087
|
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: Tameside | Statement: [Hyde, locatedIn, Tameside]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tameside Context triple: [Hyde, locatedIn, Tameside]
-
A.
Tameside
chosen
Tameside is a metropolitan borough in North West England, forming part of the Greater Manchester urban area and encompassing several towns east of Manchester city centre.
-
B.
Kirklees
Kirklees is a metropolitan borough in West Yorkshire, England, centered on the towns of Huddersfield and Dewsbury and known for its mix of urban areas and Pennine countryside.
-
C.
Salford
Salford is a city in Greater Manchester, England, known for its industrial heritage and the modern MediaCityUK development on the Salford Quays.
-
D.
Salford
Salford is a small rural village in the West Oxfordshire district of Oxfordshire, England.
-
E.
Levenshulme
Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af030114c88190b725908a32ace750 |
completed | March 9, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b589f5864881909c9fc787dd9b2341 |
completed | March 14, 2026, 4:16 p.m. |
Created at: March 9, 2026, 3:45 p.m.