Triple
T33221039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandstone, Minnesota |
E850420
|
entity |
| Predicate | hasOutdoorEvent |
P74338
|
FINISHED |
| Object | kayaking events on the Kettle River |
—
|
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: kayaking events on the Kettle River | Statement: [Sandstone, Minnesota, hasOutdoorEvent, kayaking events on the Kettle River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorEvent Context triple: [Sandstone, Minnesota, hasOutdoorEvent, kayaking events on the Kettle River]
-
A.
hasOutdoorStage
Indicates that an entity includes or is equipped with a stage located outdoors for performances or events.
-
B.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
C.
hasOutdoorResource
chosen
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
D.
hasOutdoorType
Indicates that an entity is associated with a specific type or category of outdoor environment or feature.
-
E.
hasOutdoorElements
Indicates that something includes or features components located or occurring outside, such as open-air spaces, natural features, or external structures.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:30 a.m.