Triple
T11971827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrapunctus VIII |
E284937
|
entity |
| Predicate | typicalModernInstrumentation |
P1149
|
FINISHED |
| Object | keyboard |
—
|
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: keyboard | Statement: [Contrapunctus VIII, typicalModernInstrumentation, keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalModernInstrumentation Context triple: [Contrapunctus VIII, typicalModernInstrumentation, keyboard]
-
A.
typicalInstrumentation
chosen
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
B.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
traditionalInstrument
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.