Triple
T38174681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon per tonos |
E1000172
|
entity |
| Predicate | tonalCenterAtBeginning |
P40275
|
FINISHED |
| Object | C minor |
—
|
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 minor | Statement: [Canon per tonos, tonalCenterAtBeginning, C minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tonalCenterAtBeginning Context triple: [Canon per tonos, tonalCenterAtBeginning, C minor]
-
A.
tonalCenter
chosen
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
-
B.
tonalityOfFirstMovement
Indicates the key or tonal center in which the first movement of a musical work is composed.
-
C.
tonalCharacteristic
Indicates the specific quality or character of a sound’s tone, such as its color, texture, or expressive nuance, in relation to an entity.
-
D.
tonalArchitecture
Indicates a relationship where one entity defines, shapes, or organizes the tonal structure or harmonic framework of another (such as a piece, passage, or system).
-
E.
tonal
Indicates that one entity has a tone, pitch pattern, or tonal quality in relation to another (such as a language, sound, or musical element).
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:29 p.m.