Triple
T11834307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Workington A.F.C. |
E281475
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Workington |
E90248
|
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: Workington | Statement: [Workington A.F.C., shortName, Workington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Workington Context triple: [Workington A.F.C., shortName, Workington]
-
A.
Workington
chosen
Workington is a coastal town and port on the west coast of England, historically known for its steel and coal industries and situated at the mouth of the River Derwent.
-
B.
Wooler
Wooler is a small market town and gateway to the Cheviot Hills in northern England.
-
C.
Cockermouth
Cockermouth is a historic market town in Cumbria, England, known for its Georgian architecture and literary associations, particularly with the poet William Wordsworth.
-
D.
Seascale
Seascale is a coastal village in Cumbria, England, known for its proximity to the Sellafield nuclear reprocessing and decommissioning site.
-
E.
Barrow-in-Furness
Barrow-in-Furness is a coastal industrial town in Cumbria, England, historically known for its shipbuilding and submarine construction.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f16753f4f88190940e53312aff4333 |
completed | April 29, 2026, 2:05 a.m. |
Created at: April 8, 2026, 9:43 p.m.