Triple
T11458018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrapunctus II |
E271580
|
entity |
| Predicate | intendedInstrumentation |
P29323
|
FINISHED |
| Object | unspecified |
—
|
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: unspecified | Statement: [Contrapunctus II, intendedInstrumentation, unspecified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedInstrumentation Context triple: [Contrapunctus II, intendedInstrumentation, unspecified]
-
A.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
B.
originalInstrumentation
chosen
Indicates the relationship between a musical work and the specific instruments or ensemble for which it was initially scored or conceived.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
E.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.