Triple
T32428173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trout Lake, Washington |
E828634
|
entity |
| Predicate | recreationGatewayTo |
P62286
|
FINISHED |
| Object | Mount Adams Wilderness |
—
|
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: Mount Adams Wilderness | Statement: [Trout Lake, Washington, recreationGatewayTo, Mount Adams Wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationGatewayTo Context triple: [Trout Lake, Washington, recreationGatewayTo, Mount Adams Wilderness]
-
A.
isRecreationalGateway
Indicates that something serves as an entry point or access hub for recreational activities or leisure experiences.
-
B.
recreationAccessPoint
chosen
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
C.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
-
D.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
E.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2a90da48190ada230c184bfb860 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.