Triple
T16901758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F major |
E424453
|
entity |
| Predicate | dominantTriad |
P125131
|
FINISHED |
| Object | C–E–G |
—
|
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: C–E–G | Statement: [F major, dominantTriad, C–E–G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantTriad Context triple: [F major, dominantTriad, C–E–G]
-
A.
subdominantKey
Indicates the musical key that functions as the subdominant (built on the fourth scale degree) in relation to a given tonic key.
-
B.
notableTriad
Indicates a three-way association among entities that is particularly significant, prominent, or noteworthy compared to other possible groupings.
-
C.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
-
D.
dominantForm
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
-
E.
dominantStructure
Indicates that one structure exerts primary control, influence, or prominence over other related structures within a given context.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dc7cf08190ad935935d8daf1d0 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:29 a.m.