Triple
T587985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldham borough |
E17200
|
entity |
| Predicate | hasMajorTown |
P316
|
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: [Oldham borough, hasMajorTown, Royton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royton Context triple: [Oldham borough, hasMajorTown, 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.
Banbury
Banbury is a historic market town in Oxfordshire, England, known for its medieval cross, canal-side setting, and association with the traditional Banbury cake.
-
D.
Long Ashton
Long Ashton is a village and civil parish in North Somerset, England, located just southwest of Bristol.
-
E.
Telford
Telford is a given name most notably associated with Telford Taylor, the American lawyer and chief prosecutor at the Nuremberg Trials.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9d1e68819096a9b5e7b2e83d6e |
completed | March 1, 2026, 8:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a64a48e53081908e5d5e093edb5e75 |
completed | March 3, 2026, 2:41 a.m. |
Created at: March 1, 2026, 7:33 p.m.