Triple
T8014303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker Lake Trail |
E186571
|
entity |
| Predicate | hasDestinationType |
P2066
|
FINISHED |
| Object | mountain lake |
—
|
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: mountain lake | Statement: [Baker Lake Trail, hasDestinationType, mountain lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDestinationType Context triple: [Baker Lake Trail, hasDestinationType, mountain lake]
-
A.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
B.
isDestinationFor
chosen
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
C.
hasPrivateDestination
Indicates that an entity is associated with a destination that is not publicly accessible or is intended for restricted/private use.
-
D.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
E.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df0f4bc8190ae87586972018085 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.