Triple
T13904905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shard Bridge |
E334322
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Fylde |
E333682
|
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: Fylde | Statement: [Shard Bridge, connects, Fylde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fylde Context triple: [Shard Bridge, connects, Fylde]
-
A.
Fylde Coast
The Fylde Coast is a coastal region in Lancashire, England, encompassing seaside towns such as Blackpool, Fleetwood, and Lytham St Annes along the Irish Sea.
-
B.
Fylde district
chosen
Fylde district is a local government district in Lancashire, England, known for its coastal towns, rural landscapes, and proximity to the River Wyre.
-
C.
Forfarshire
Forfarshire is the former historic name of the Scottish county now known as Angus.
-
D.
Angus coast
The Angus coast is a stretch of shoreline in eastern Scotland facing the North Sea, known for its sandy beaches, cliffs, and fishing towns between Dundee and Montrose.
-
E.
Fife coast
The Fife coast is a scenic stretch of shoreline in eastern Scotland, known for its fishing villages, sandy beaches, and part of the Fife Coastal Path.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25db1e308190aaed6a21e443cc44 |
completed | April 14, 2026, 11:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac8401b88190a2e87dbdf1bbaee2 |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:16 p.m.