Triple
T27441784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skelwith Bridge |
E690954
|
entity |
| Predicate | distanceToAmbleside |
P200020
|
FINISHED |
| Object | approximately 3 miles |
—
|
LITERAL 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: approximately 3 miles | Statement: [Skelwith Bridge, distanceToAmbleside, approximately 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAmbleside Context triple: [Skelwith Bridge, distanceToAmbleside, approximately 3 miles]
-
A.
distanceToAmesbury
Indicates the spatial distance between a given entity and the location of Amesbury.
-
B.
distanceToCockermouth
Indicates the measured or specified distance between a given entity or location and Cockermouth.
-
C.
distanceToOswestry
Indicates the spatial distance between a given entity and the location of Oswestry.
-
D.
distanceToKeswick
Indicates the spatial distance between a given entity and the location named Keswick.
-
E.
distanceToDovedale
Indicates the spatial distance between a given entity and the location Dovedale.
- F. None of above. chosen
Provenance (4 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:45 p.m.