Triple
T22774230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keld |
E563647
|
entity |
| Predicate | hasNearbyTrailJunction |
P144021
|
FINISHED |
| Object | junction of Coast to Coast Walk and Pennine Way |
—
|
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: junction of Coast to Coast Walk and Pennine Way | Statement: [Keld, hasNearbyTrailJunction, junction of Coast to Coast Walk and Pennine Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTrailJunction Context triple: [Keld, hasNearbyTrailJunction, junction of Coast to Coast Walk and Pennine Way]
-
A.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
B.
hasNearbyTrailFeature
chosen
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
C.
hasNearbyTrailType
Indicates that one entity has another entity of a specified trail type located in close proximity to it.
-
D.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
E.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
- F. None of above.
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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b60eec48190b0aaf3eb7ede38d4 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.