Triple
T13080554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A589 road |
E310189
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Morecambe |
E40592
|
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: Morecambe | Statement: [A589 road, connects, Morecambe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morecambe Context triple: [A589 road, connects, Morecambe]
-
A.
Morecambe
chosen
Morecambe is a seaside resort town on the coast of Morecambe Bay in north-west England, known for its promenade, beaches, and views across the bay to the Lake District.
-
B.
Blackpool
Blackpool is a famous seaside resort town in northwest England known for its beach, promenade, and landmark Blackpool Tower.
-
C.
Blackpool
Blackpool is a small coastal settlement on Waiheke Island in New Zealand, known for its beach and relaxed residential character.
-
D.
Grimsby
Grimsby is a large coastal town and historic fishing port in North East Lincolnshire, England, known for its maritime heritage and seafood industry.
-
E.
Grimsby
Grimsby is a town in Ontario, Canada, located on the southern shore of Lake Ontario between Hamilton and St. Catharines.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98119cb7081908b78ffe83ec99851 |
completed | April 10, 2026, 11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d60c603881909dff49f4356042b5 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9:01 p.m.