Triple
T15779487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton Creek |
E382574
|
entity |
| Predicate | recreationRisk |
P82346
|
FINISHED |
| Object | flashy streamflows during storms |
—
|
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: flashy streamflows during storms | Statement: [Newton Creek, recreationRisk, flashy streamflows during storms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationRisk Context triple: [Newton Creek, recreationRisk, flashy streamflows during storms]
-
A.
hasRecreationDifficulty
Indicates the level of challenge or effort required to engage in a particular recreational activity or experience.
-
B.
recreationUseLevel
Indicates the intensity or degree to which an entity is used for recreational activities.
-
C.
safetyChallenge
chosen
Indicates that one entity presents or poses a safety-related test, risk, or concern to another entity.
-
D.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
E.
explorationRisk
Indicates the degree of potential danger, uncertainty, or adverse outcomes associated with undertaking an exploration activity or venture.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e053fea90081908e3fe4f91475bead |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.