Triple
T23298694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freygish |
E590241
|
entity |
| Predicate | hasScaleDegreePattern |
P70299
|
FINISHED |
| Object | 1–b2–3–4–5–b6–b7 |
—
|
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: 1–b2–3–4–5–b6–b7 | Statement: [Freygish, hasScaleDegreePattern, 1–b2–3–4–5–b6–b7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScaleDegreePattern Context triple: [Freygish, hasScaleDegreePattern, 1–b2–3–4–5–b6–b7]
-
A.
typicalScaleDegreePattern
chosen
Indicates the usual or most common sequence of scale degrees that characterizes a particular melodic, harmonic, or stylistic pattern.
-
B.
scaleDegree7
Indicates that one musical pitch or chord functions as the seventh scale degree in relation to a given tonal center or key.
-
C.
diatonicScale
Indicates that a musical element (such as a note, chord, or melody) belongs to or is derived from a specific diatonic scale.
-
D.
scaleDegree5
Indicates that one musical pitch or chord stands in the functional role of the fifth scale degree (dominant) relative to a given tonal center.
-
E.
scaleDegree6
Indicates that one musical pitch or chord functions as the sixth degree of a scale relative to a given tonal center.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d133448190bf350a9f51c1531c |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:03 p.m.