Triple
T27441785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skelwith Bridge |
E690954
|
entity |
| Predicate | distanceToConiston |
P200042
|
FINISHED |
| Object | approximately 6 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 6 miles | Statement: [Skelwith Bridge, distanceToConiston, approximately 6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToConiston Context triple: [Skelwith Bridge, distanceToConiston, approximately 6 miles]
-
A.
distanceToCockermouth
Indicates the measured or specified distance between a given entity or location and Cockermouth.
-
B.
distanceToBodmin
Indicates the spatial distance between an entity and the location Bodmin.
-
C.
distanceToBarnstaple
Indicates the spatial distance between a given entity and the location of Barnstaple.
-
D.
distanceFromLiskeard
Indicates the measured distance between a given location and the town of Liskeard.
-
E.
distanceToAmbleside
Indicates the spatial distance between a given location or object and Ambleside.
- 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_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
| PDg | Predicate description generation | batch_69ff6eefa9c48190aac36916990f6db5 |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 27, 2026, 12:45 p.m.