Triple
T12688310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Chelan National Recreation Area |
E303130
|
entity |
| Predicate | hasTrailheadAccessVia |
P30481
|
FINISHED |
| Object | Lake Chelan boat service |
—
|
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: Lake Chelan boat service | Statement: [Lake Chelan National Recreation Area, hasTrailheadAccessVia, Lake Chelan boat service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailheadAccessVia Context triple: [Lake Chelan National Recreation Area, hasTrailheadAccessVia, Lake Chelan boat service]
-
A.
hasTrailheadAt
Indicates that a trail or route begins or has its official starting point at a specified location.
-
B.
accessTrailhead
chosen
Indicates that an entity has a way to reach or enter a specific trailhead location.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
hasTrailAccessPoint
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
E.
hasTrailheadSignage
Indicates that a trailhead is equipped with signage providing information or guidance to users.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.