Triple
T25270745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crowden |
E633560
|
entity |
| Predicate | trailJunction |
P36754
|
FINISHED |
| Object | Pennine Way long-distance footpath |
E94827
|
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: Pennine Way long-distance footpath | Statement: [Crowden, trailJunction, Pennine Way long-distance footpath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailJunction Context triple: [Crowden, trailJunction, Pennine Way long-distance footpath]
-
A.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
B.
transportationJunctionFor
chosen
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
C.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
D.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
E.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
- F. None of above.
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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba1a1f88190b3db79ec06bfa994 |
completed | May 1, 2026, 11:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10896f9a8081908edb3db726d26589 |
completed | May 22, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:16 p.m.