Triple
T29789978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E major |
E756375
|
entity |
| Predicate | commonChordSpelling |
P194181
|
FINISHED |
| Object | E–G#–B |
—
|
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: E–G#–B | Statement: [E major, commonChordSpelling, E–G#–B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonChordSpelling Context triple: [E major, commonChordSpelling, E–G#–B]
-
A.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
-
B.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
C.
usesFixedSpellingsForCommonSyllables
Indicates that an entity consistently applies predetermined, standard spellings for frequently occurring syllables.
-
D.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
E.
typicalIChord
Indicates that a chord is a standard or characteristic instance of the I (tonic) chord within a given musical 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: April 29, 2026, 5:12 p.m.