Triple
T37975376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumi school |
E947407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional performing arts lineage |
C17294
|
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: traditional performing arts lineage Context triple: [Izumi school, instanceOf, traditional performing arts lineage]
-
A.
traditional theatre
chosen
Traditional theatre is a live performing art form in which actors present scripted stories on stage using established cultural conventions, such as stylized movement, costumes, music, and dialogue, often rooted in historical or regional traditions.
-
B.
traditional dance
A traditional dance is a culturally rooted form of movement and expression passed down through generations, often performed during rituals, celebrations, or community gatherings to preserve and convey shared heritage and values.
-
C.
live music tradition
A live music tradition is a culturally rooted, recurring practice of performing music in real time before an audience, often passed down through generations and shaped by shared rituals, venues, and community participation.
-
D.
visual art tradition
A visual art tradition is a historically and culturally rooted set of shared practices, styles, techniques, and aesthetic values that guide the creation and interpretation of visual artworks within a particular community or lineage.
-
E.
operatic tradition
Operatic tradition is the historically evolved set of musical, theatrical, and cultural practices, conventions, and repertoires that shape how opera is composed, performed, and experienced across time and place.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.