Triple
T10124886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford services |
E226185
|
entity |
| Predicate | servesTrafficDirection |
P48943
|
FINISHED |
| Object | northbound |
—
|
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: northbound | Statement: [Oxford services, servesTrafficDirection, northbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTrafficDirection Context triple: [Oxford services, servesTrafficDirection, northbound]
-
A.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
B.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
C.
servedByDirection
chosen
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
servesSeasonalTraffic
Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ebe4548190a484c145639d92f0 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.