Triple
T25973753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bootham Bar |
E645877
|
entity |
| Predicate | controlsRouteTo |
P119112
|
FINISHED |
| Object | northern approach to York |
—
|
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: northern approach to York | Statement: [Bootham Bar, controlsRouteTo, northern approach to York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsRouteTo Context triple: [Bootham Bar, controlsRouteTo, northern approach to York]
-
A.
controlsRoute
chosen
Indicates that one entity has authority over or manages the path, course, or routing taken by another entity.
-
B.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
C.
connectedRoute
Indicates that there is a direct or logically continuous path linking two locations or segments within a network.
-
D.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
-
E.
routeTargeted
Indicates that a route is specifically directed toward or intended to reach a particular target entity or destination.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 22, 2026, 8:51 a.m.