Triple
T5373976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Hood's Bay |
E108915
|
entity |
| Predicate | walkingRoute |
P17534
|
FINISHED |
| Object | on the route of the Cleveland Way National Trail |
—
|
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: on the route of the Cleveland Way National Trail | Statement: [Robin Hood's Bay, walkingRoute, on the route of the Cleveland Way National Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkingRoute Context triple: [Robin Hood's Bay, walkingRoute, on the route of the Cleveland Way National Trail]
-
A.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
B.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
C.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
D.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
popularRouteFrom
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.