Triple
T17372444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potteries Loop Line |
E422350
|
entity |
| Predicate | served |
P17148
|
FINISHED |
| Object | Tunstall |
—
|
NE ONNED1 |
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: Tunstall | Statement: [Potteries Loop Line, served, Tunstall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tunstall Context triple: [Potteries Loop Line, served, Tunstall]
-
A.
Tunstall
chosen
Tunstall is one of the six towns that make up the city of Stoke-on-Trent in Staffordshire, England, known historically for its pottery industry.
-
B.
Tunstall
Tunstall is a small rural village located in the Holderness area of the East Riding of Yorkshire, England.
-
C.
Tilbury
Tilbury is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known for its agricultural surroundings and local services.
-
D.
Tilbury
Tilbury is a port town on the north bank of the River Thames in Essex, England, known for its docks and historic forts guarding the approach to London.
-
E.
Dunstable
Dunstable is a historic market town in Bedfordshire, England, known for its location at the crossroads of ancient routes and its proximity to the Chiltern Hills.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a69d93c81908ce2d909857a3a11 |
completed | April 19, 2026, 2:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a019568a27c8190af1bbe6db75f3e6f |
in_progress | May 11, 2026, 8:38 a.m. |
Created at: April 10, 2026, 5:44 a.m.