Triple
T3584762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire |
E75882
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Bridlington |
E282446
|
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: Bridlington | Statement: [Yorkshire, hasTown, Bridlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bridlington Context triple: [Yorkshire, hasTown, Bridlington]
-
A.
Bridlington
chosen
Bridlington is a coastal town and popular seaside resort on the North Sea in the East Riding of Yorkshire, England.
-
B.
Barton-on-Humber
Barton-on-Humber is a small historic town in North Lincolnshire, England, situated on the south bank of the Humber Estuary.
-
C.
Sowerby Bridge
Sowerby Bridge is a market town in Calderdale, West Yorkshire, England, known for its industrial heritage, canal and railway junctions, and position in the Upper Calder Valley.
-
D.
Skegness
Skegness is a seaside town and popular holiday resort on the east coast of England.
-
E.
Hartlepool
Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc10f9b508190bde4a4e4711dd452 |
completed | March 8, 2026, 6:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b402fcc5f481909c66319f75a8dc85 |
completed | March 13, 2026, 12:28 p.m. |
Created at: March 8, 2026, 3:22 p.m.