Triple
T5408166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Landranger 89 |
E120944
|
entity |
| Predicate | hasRightsOfWay |
P29688
|
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: [OS Landranger 89, hasRightsOfWay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightsOfWay Context triple: [OS Landranger 89, hasRightsOfWay, true]
-
A.
ownerOfRightOfWay
Indicates that one entity holds the legal right to pass through or use a specific path, route, or area on another entity’s property.
-
B.
hasRightOfWay
chosen
Indicates that one entity is entitled to proceed or act before another in a shared space or interaction, without having to yield.
-
C.
someRightOfWayUsedBy
Indicates that a particular right of way is utilized or traversed by a specified user, route, or transport entity.
-
D.
operatesOnFormerRightOfWayOf
Indicates that an entity (such as a route, line, or facility) runs along or uses the previous right-of-way corridor that was once occupied by another transportation or infrastructure alignment.
-
E.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8794e0c4819082bebf2da5e41201 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.