Triple
T38174566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuga canonica in epidiapente |
E1000169
|
entity |
| Predicate | tonalOrganization |
P150766
|
FINISHED |
| Object | contrapuntal |
—
|
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: contrapuntal | Statement: [Fuga canonica in epidiapente, tonalOrganization, contrapuntal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tonalOrganization Context triple: [Fuga canonica in epidiapente, tonalOrganization, contrapuntal]
-
A.
tonalArchitecture
chosen
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).
-
B.
tonalAssociation
Indicates a relationship where one entity is linked to another through a shared or corresponding tonal quality, pitch, or key.
-
C.
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).
-
D.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
-
E.
tonalFeatures
Indicates that one entity specifies or characterizes the tonal properties or qualities associated with another entity.
- 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_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.