Triple
T37819976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawn Wall route |
E942881
|
entity |
| Predicate | notablePitchDifficulty |
—
|
GENERATED |
| Object | multiple 5.14d pitches |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePitchDifficulty Context triple: [Dawn Wall route, notablePitchDifficulty, multiple 5.14d pitches]
-
A.
notablePitch
Indicates that an entity is recognized for having a particularly significant or noteworthy pitch, offer, or proposal in a given context.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
usedPitch
Indicates that a particular pitch (musical note or frequency) was employed or applied in a given context or action.
-
D.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
-
E.
notableRiff
Indicates that an entity is recognized for having a distinctive, memorable, or influential musical riff associated with it.
- F. None of above. chosen
Provenance (1 batch)
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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.