Triple
T9917941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longridge |
E185916
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Longridge Fell (nearby) |
E703628
|
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: Longridge Fell (nearby) | Statement: [Longridge, hasLandmark, Longridge Fell (nearby)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longridge Fell (nearby) Context triple: [Longridge, hasLandmark, Longridge Fell (nearby)]
-
A.
Longridge Fell
chosen
Longridge Fell is a prominent hill and the most southerly fell in England’s Forest of Bowland, known for its panoramic views over Lancashire.
-
B.
Mickle Fell
Mickle Fell is a prominent hill in northern England and one of the highest points in the Pennines.
-
C.
Brim Fell
Brim Fell is a Lake District fell in Cumbria, England, forming part of the Coniston Fells range and popular with hikers for its scenic ridgeline and views.
-
D.
Loughrigg Fell
Loughrigg Fell is a popular low fell in England’s Lake District known for its accessible walking routes and panoramic views over nearby lakes and valleys.
-
E.
Place Fell
Place Fell is a prominent fell in England's Lake District, offering scenic hiking routes and expansive views over Ullswater and the surrounding valleys.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5673f108190914e0c172dddc65f |
completed | April 2, 2026, 12:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20dec42848190ab9f8663155df83f |
completed | April 5, 2026, 7:23 a.m. |
Created at: March 30, 2026, 8:42 p.m.