Triple
T21320120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langdale Fells |
E525588
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Esk Pike |
—
|
NE NERFINISHED |
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: Esk Pike | Statement: [Langdale Fells, hasPart, Esk Pike]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esk Pike Context triple: [Langdale Fells, hasPart, Esk Pike]
-
A.
Esk Pike
chosen
Esk Pike is a prominent fell in England’s Lake District, known for its rugged terrain and panoramic views over the surrounding Cumbrian peaks and valleys.
-
B.
Pieries Peak
Pieries Peak is a notable summit within New South Wales’ Mount Royal National Park, known for its bushwalking opportunities and natural bushland scenery.
-
C.
Heron Pike
Heron Pike is a fell in England’s Lake District, forming part of the Eastern Fells and offering popular walking routes with views over Grasmere and Rydal Water.
-
D.
Hyndman Peak
Hyndman Peak is a prominent mountain summit in central Idaho known for its challenging climbs and scenic alpine views.
-
E.
Boistfort Peak
Boistfort Peak is the highest summit in southwestern Washington’s Willapa Hills, known for its forested slopes and regional prominence.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ecfb7d481909cb73f95c3ddd9ed |
completed | April 21, 2026, 1:42 p.m. |
Created at: April 16, 2026, 4:39 p.m.