Triple
T4098685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvellyn |
E87885
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Cumbria |
E14179
|
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: Cumbria | Statement: [Helvellyn, locatedIn, Cumbria]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cumbria Context triple: [Helvellyn, locatedIn, Cumbria]
-
A.
Cumbria
chosen
Cumbria is a largely rural county in North West England known for its dramatic landscapes, including most of the Lake District National Park.
-
B.
Westmorland
Westmorland is a small city in Southern California’s Imperial Valley, known for its agricultural surroundings and proximity to the Salton Sea.
-
C.
Northumberland
Northumberland is a historic and largely rural county in northeast England, known for its rugged coastline, medieval castles, and significant Roman heritage.
-
D.
Northumberland
Northumberland is a small rural town in Saratoga County, New York, known for its agricultural character and proximity to the Hudson River.
-
E.
Westmorland and Furness
Westmorland and Furness is a unitary authority area in Cumbria, England, formed in 2023 as part of local government reorganization.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b725788819091c6aaeccfb86964 |
completed | March 14, 2026, 2:06 p.m. |
Created at: March 9, 2026, 3:40 p.m.