Triple
T33068523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapperton Tunnel |
E846167
|
entity |
| Predicate | hasNoTowpath |
P203422
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sapperton Tunnel, hasNoTowpath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoTowpath Context triple: [Sapperton Tunnel, hasNoTowpath, true]
-
A.
hasTowpath
Indicates that a waterway or canal is accompanied by a path running alongside it, typically used for towing boats.
-
B.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
-
C.
hasBikeTrailAccess
Indicates that an entity has direct access to, or is connected with, a bike trail suitable for cycling.
-
D.
hasNoRoadToSummit
Indicates that there is no road providing direct access to the summit of a specified location or feature.
-
E.
hasHikingAccess
Indicates that one location or entity provides access or a connection to hiking trails or hiking areas.
- F. None of above. chosen
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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a017a360f088190acd5933aa353e763 |
completed | May 11, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_6a0179d3f78c8190b1d2e8829619fa54 |
completed | May 11, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_6a017a354d648190b036e9dad3211857 |
completed | May 11, 2026, 6:41 a.m. |
Created at: May 1, 2026, 1:25 a.m.