Triple
T12901222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hood Skibowl |
E308615
|
entity |
| Predicate | hasRunDifficulty |
P24163
|
FINISHED |
| Object | beginner |
—
|
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: beginner | Statement: [Mount Hood Skibowl, hasRunDifficulty, beginner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunDifficulty Context triple: [Mount Hood Skibowl, hasRunDifficulty, beginner]
-
A.
hasRunDifficultyDistribution
Indicates that there is an associated distribution describing how difficult different runs or executions of a process or activity are.
-
B.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
C.
hasMeasurementDifficulty
Indicates that performing a measurement on something is challenging or problematic in some way.
-
D.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
E.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.