Triple
T16849680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royton Town Hall |
E409637
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Royton |
E83854
|
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: Royton | Statement: [Royton Town Hall, locatedIn, Royton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royton Context triple: [Royton Town Hall, locatedIn, Royton]
-
A.
Royton
chosen
Royton is a town in Greater Manchester, England, historically part of Lancashire and now within the Metropolitan Borough of Oldham.
-
B.
Timperley
Timperley is a suburban village within the Metropolitan Borough of Trafford in Greater Manchester, England, known for its residential character and commuter links to Manchester.
-
C.
Yate
Yate is a town in South Gloucestershire, England, known as a residential and commercial centre north of Bristol.
-
D.
Banwell
Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
-
E.
Wellesbourne
Wellesbourne is a large English village in Warwickshire, known for its historic airfield and proximity to Stratford-upon-Avon.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b377b5d881909f0878dd9957f3bc |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb1f02648190937c692af83843dc |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.