Triple
T28956753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E15 |
E731183
|
entity |
| Predicate | linkedToNationalRoute |
P152080
|
FINISHED |
| Object | A9 motorway (Scotland) |
—
|
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: A9 motorway (Scotland) | Statement: [European route E15, linkedToNationalRoute, A9 motorway (Scotland)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToNationalRoute Context triple: [European route E15, linkedToNationalRoute, A9 motorway (Scotland)]
-
A.
isKeyNationalRouteFor
Indicates that one route serves as a primary or strategically important national connection for another route or network.
-
B.
isSegmentOfNationalRoute
Indicates that a road segment forms part of a designated national route within a country's road network.
-
C.
servedByNationalRoute
chosen
Indicates that a location or facility is connected to and accessible via a specified national route.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
hasNationalRoad
Indicates that a location is connected to or served by a designated national road within a country's official road network.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 8:48 a.m.