Triple
T14820405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardsea |
E348434
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Furness |
E1115996
|
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: Furness | Statement: [Bardsea, region, Furness]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Furness Context triple: [Bardsea, region, Furness]
-
A.
Furness
Furness is an English-origin surname borne by various notable figures, including scholars, architects, and public officials.
-
B.
Furness
chosen
Furness is a peninsula and historic region in Cumbria, England, known for its industrial heritage, coastal landscapes, and proximity to the Lake District.
-
C.
Furness Vale
Furness Vale is a small village in Derbyshire, England, situated in the High Peak area of the Peak District.
-
D.
Barrow and Furness
Barrow and Furness is a UK parliamentary constituency in Cumbria that includes the industrial town of Barrow-in-Furness and surrounding areas.
-
E.
High Furness
High Furness is the upland, largely rural and scenic northern part of the Furness Peninsula in Cumbria, England, known for its fells, forests, and proximity to the Lake District.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe4cf38819090f25ef045351d5d |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389bc06c8190a8269c07677d9c35 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:50 a.m.