Triple
T29789979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E major |
E756375
|
entity |
| Predicate | diatonicTriads |
P167878
|
FINISHED |
| Object | E major |
—
|
NE NERFINISHED |
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: E major | Statement: [E major, diatonicTriads, E major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diatonicTriads Context triple: [E major, diatonicTriads, E major]
-
A.
diatonicScale
Indicates that a musical element (such as a note, chord, or melody) belongs to or is derived from a specific diatonic scale.
-
B.
diatonicChordCount
Indicates the number of chords in a given context that are built solely from the notes of a specified diatonic scale.
-
C.
dominantTriad
Indicates that one entity forms the primary or controlling component within a three-part (triadic) relationship involving the other two entities.
-
D.
diatonicTriadOnVI
Indicates that a diatonic triad is built on the sixth scale degree (VI) within a given key.
-
E.
leadingToneTriad
Indicates a triad built on the leading tone (the seventh scale degree) that functions to resolve toward the tonic harmony.
- F. None of above. chosen
Provenance (4 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e1f0dc8190a9663a93706267b5 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:12 p.m.