Triple
T27050937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra |
E684770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online collaborative music project |
C12274
|
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: online collaborative music project Context triple: [YouTube Symphony Orchestra, instanceOf, online collaborative music project]
-
A.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
B.
avant-garde music project
An avant-garde music project is an experimental artistic endeavor that challenges conventional musical structures and aesthetics through innovative sounds, techniques, and interdisciplinary concepts.
-
C.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
-
D.
rock music collaboration
A rock music collaboration is a creative partnership where two or more artists, bands, or producers from the rock genre work together to write, perform, or record shared musical projects.
-
E.
live musical project
A live musical project is a performance-focused endeavor in which musicians present music in real time to an audience, often incorporating unique arrangements, improvisation, and collaborative elements distinct from studio recordings.
- F. None of above.
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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:14 a.m.