Triple
T31444013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwanese gezaixi |
E802141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Taiwanese opera form |
C37155
|
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 Taiwanese opera form Context triple: [Taiwanese gezaixi, instanceOf, traditional Taiwanese opera form]
-
A.
Peking opera artist
A Peking opera artist is a highly trained performer who combines stylized singing, speech, dance, acrobatics, and symbolic gestures to portray traditional Chinese opera roles within the codified aesthetic of Peking opera.
-
B.
Chinese theater
chosen
Chinese theater is a traditional performing art form that combines stylized acting, music, dance, acrobatics, elaborate costumes, and symbolic makeup to tell stories drawn from history, folklore, and classical literature.
-
C.
traditional Malay musical form
A traditional Malay musical form is a culturally rooted style of music-making that combines characteristic melodies, rhythms, instruments, and performance practices to express Malay heritage and social life.
-
D.
Cantonese opera singer
A Cantonese opera singer is a performer who specializes in singing, acting, and stylized movement within the traditional Cantonese opera art form, using distinct vocal techniques, costumes, and gestures to portray classical roles and stories.
-
E.
Bhojpuri theatre form
Bhojpuri theatre form is a regional dramatic tradition from the Bhojpuri-speaking areas of India and Nepal that blends folk music, dance, and storytelling to depict local life, social issues, and cultural values.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:08 p.m.