Triple
T17373301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche Gulch |
E422368
|
entity |
| Predicate | bestConditions |
P114092
|
FINISHED |
| Object | firm morning snowpack |
—
|
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: firm morning snowpack | Statement: [Avalanche Gulch, bestConditions, firm morning snowpack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestConditions Context triple: [Avalanche Gulch, bestConditions, firm morning snowpack]
-
A.
featuresCondition
chosen
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
B.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
C.
definesConditionsFor
Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
-
D.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
E.
conditionsDescribedAs
Indicates that one entity is described or characterized in terms of certain conditions specified by another entity.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6a9ec881908bfe49413826d37e |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.