Triple
T22646402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilterns Cycleway |
E558975
|
entity |
| Predicate | followsRouteType |
P13326
|
FINISHED |
| Object | on-road cycle route |
—
|
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-road cycle route | Statement: [Chilterns Cycleway, followsRouteType, on-road cycle route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRouteType Context triple: [Chilterns Cycleway, followsRouteType, on-road cycle route]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
followsPlanType
Indicates that one entity adheres to, or is carried out according to, a specified type of plan.
-
D.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
E.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170382ba48190b77692762db43313 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.