Triple
T28695723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cringle Moor |
E729409
|
entity |
| Predicate | onLongDistancePath |
P28904
|
FINISHED |
| Object | Cleveland Way National Trail |
—
|
NE NERFINISHED |
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: Cleveland Way National Trail | Statement: [Cringle Moor, onLongDistancePath, Cleveland Way National Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onLongDistancePath Context triple: [Cringle Moor, onLongDistancePath, Cleveland Way National Trail]
-
A.
hasLongDistancePathAccess
Indicates that an entity has the ability or right to use a path or route that spans a long distance.
-
B.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
C.
longDistanceTrail
chosen
Indicates that a trail or route spans a considerable distance, typically intended for extended or multi-day travel.
-
D.
longDistanceService
Indicates that a service operates over large geographic distances, typically connecting locations that are far apart rather than nearby.
-
E.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656af1dec8190a5ad3298de3cb914 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:39 a.m.