Triple
T28752883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seeley Lake |
E731579
|
entity |
| Predicate | isPartOfTouringRoute |
P17534
|
FINISHED |
| Object | Seeley–Swan scenic corridor |
—
|
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: Seeley–Swan scenic corridor | Statement: [Seeley Lake, isPartOfTouringRoute, Seeley–Swan scenic corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTouringRoute Context triple: [Seeley Lake, isPartOfTouringRoute, Seeley–Swan scenic corridor]
-
A.
isMajorTourismRoute
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
B.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
D.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
E.
isScenicRouteOnWayTo
Indicates that a particular route is visually appealing and lies along the path between a starting point and a 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 28, 2026, 6:08 a.m.