Triple
T24604527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | intonarumori |
E608928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental musical instrument |
C48496
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: experimental musical instrument Context triple: [intonarumori, instanceOf, experimental musical instrument]
-
A.
experimental musical
An experimental musical is a theatrical work that challenges traditional musical conventions through unconventional storytelling, innovative music and sound design, and nonstandard structures or performance techniques.
-
B.
experimental music composition
Experimental music composition is the creation of sound works that deliberately challenge or expand traditional musical structures, techniques, and listening expectations through innovative, unconventional, or exploratory approaches.
-
C.
experimental music act
An experimental music act is a musical project or group that deliberately challenges conventional structures, sounds, and performance practices to explore new, unconventional, or avant-garde sonic possibilities.
-
D.
student-built instrument
A student-built instrument is a musical device designed and constructed by learners, often using accessible materials, to explore sound production, creativity, and hands-on engineering or artistic principles.
-
E.
experimental music scene
The experimental music scene is a loosely connected community of artists, venues, and audiences dedicated to exploring unconventional sounds, structures, and performance practices that challenge mainstream musical norms.
- F. None of above. chosen
Provenance (1 batch)
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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:31 a.m.