Triple
T24562356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Highlands |
E607688
|
entity |
| Predicate | tourismRoutePassesThrough |
P17534
|
FINISHED |
| Object | North Coast 500 |
E315221
|
NE 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: North Coast 500 | Statement: [Northwest Highlands, tourismRoutePassesThrough, North Coast 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismRoutePassesThrough Context triple: [Northwest Highlands, tourismRoutePassesThrough, North Coast 500]
-
A.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
isMajorTourismRoute
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
C.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
D.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
E.
tourismCorridor
Indicates a designated route or area that links multiple destinations to facilitate and promote tourism-related movement and activities between them.
- F. None of above.
Provenance (4 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f7a244819080596718c21d0df3 |
completed | April 30, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ff8670b94819094c7c2de869b23ae |
completed | May 22, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.