Triple
T38599255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C major |
E934164
|
entity |
| Predicate | hasPitchClassSet |
P191277
|
FINISHED |
| Object | {C, D, E, F, G, A, 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: {C, D, E, F, G, A, B} | Statement: [C major, hasPitchClassSet, {C, D, E, F, G, A, B}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchClassSet
Context triple: [C major, hasPitchClassSet, {C, D, E, F, G, A, B}]
-
A.
hasPitchCount
Indicates that an entity is associated with a specific number of pitches, representing how many pitches have occurred or been recorded for it.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
hasPitchLength
Indicates that an entity (such as a field or pitch) is associated with a specific measurement of its length.
-
D.
hasKeySignatureDistribution
Indicates that there is a specific pattern or spread of key signatures associated with the entity, describing how frequently or prominently different key signatures occur.
-
E.
hasPitchShape
Indicates that one entity possesses or exhibits a particular contour, form, or configuration of pitch.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.