Triple
T20860571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayfield, Derbyshire |
E513604
|
entity |
| Predicate | hasRightOfWayNetwork |
P142148
|
FINISHED |
| Object | public footpaths |
—
|
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: public footpaths | Statement: [Hayfield, Derbyshire, hasRightOfWayNetwork, public footpaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightOfWayNetwork Context triple: [Hayfield, Derbyshire, hasRightOfWayNetwork, public footpaths]
-
A.
hasRightOfWay
Indicates that one entity is entitled to proceed or act before another in a shared space or interaction, without having to yield.
-
B.
hasTypicalRightOfWay
Indicates that one party customarily has the legal or expected priority to proceed or pass before another in a given situation.
-
C.
someRightOfWayUsedBy
Indicates that a particular right of way is utilized or traversed by a specified user, route, or transport entity.
-
D.
hadRightOfWay
Indicates that one party was entitled, by rule or law, to proceed first or continue without yielding in a shared space or traffic situation.
-
E.
hasRightOfWaySeparation
Indicates that one entity is required to maintain a specified right-of-way distance or separation from another entity.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3aba3d0819093431f38f0095a71 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:44 p.m.