Triple
T25342678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tissington |
E635457
|
entity |
| Predicate | hasRouteNearby |
P76707
|
FINISHED |
| Object | Tissington 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: Tissington Trail | Statement: [Tissington, hasRouteNearby, Tissington Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNearby Context triple: [Tissington, hasRouteNearby, Tissington Trail]
-
A.
hasNearbyWalkingRoutes
chosen
Indicates that there are walkable paths or routes located close to the referenced entity.
-
B.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
C.
hasNearbyCycleRoute
Indicates that an entity is located close to a designated cycling route or path.
-
D.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
E.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:32 p.m.