Triple
T19957676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North West 200 |
E479726
|
entity |
| Predicate | usesRoad |
P20522
|
FINISHED |
| Object | A2 coast road |
—
|
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: A2 coast road | Statement: [North West 200, usesRoad, A2 coast road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoad Context triple: [North West 200, usesRoad, A2 coast road]
-
A.
onRoad
chosen
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
B.
appliesToRoad
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a road.
-
C.
isRoadPass
Indicates that a particular road or route is currently passable or open for travel.
-
D.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af1b32c81908ebe0e2570ec06a9 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.