Triple
T16943931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalama River |
E411018
|
entity |
| Predicate | recreationSiteFor |
P95328
|
FINISHED |
| Object | anglers |
—
|
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: anglers | Statement: [Kalama River, recreationSiteFor, anglers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationSiteFor Context triple: [Kalama River, recreationSiteFor, anglers]
-
A.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
B.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
C.
operatorOfRecreationArea
Indicates that an entity is responsible for managing, running, or overseeing the operations of a recreation area.
-
D.
explorationSiteOf
Indicates that a location or site is the place where a particular exploration activity, mission, or project is conducted or associated.
-
E.
recreationRegion
chosen
Indicates that a location or area is designated or used as a region for recreational activities.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb08da88190b07c32652bbc1534 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.