Triple
T33575622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A minor |
E860021
|
entity |
| Predicate | subdominant |
P99488
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [A minor, subdominant, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdominant Context triple: [A minor, subdominant, D]
-
A.
subdominantKey
chosen
Indicates the musical key that functions as the subdominant (built on the fourth scale degree) in relation to a given tonic key.
-
B.
dominantTone
Indicates the primary or most prominent emotional or stylistic tone that characterizes something in relation to other possible tones.
-
C.
dominantNote
Indicates that one note functions as the dominant (fifth scale degree) in relation to another note, typically resolving to it harmonically.
-
D.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
-
E.
dominantForm
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74b95248190a3546b33dda2402d |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.