Triple
T32383294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guan Hanqing (play) |
E827478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese historical drama play |
C53722
|
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: Chinese historical drama play Context triple: [Guan Hanqing (play), instanceOf, Chinese historical drama play]
-
A.
Ming dynasty drama
Ming dynasty drama refers to the diverse body of Chinese theatrical works produced during the Ming dynasty (1368–1644), characterized by elaborate poetic language, complex plots, and a blend of Confucian moral themes with romantic and historical narratives.
-
B.
Ming dynasty play
chosen
A Ming dynasty play is a traditional Chinese dramatic work from the Ming period (1368–1644), typically combining poetic dialogue, music, dance, and elaborate staging to depict historical, romantic, or moral themes.
-
C.
Chinese theater
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.
-
D.
Chinese historical novel
A Chinese historical novel is a long-form narrative that dramatizes events, figures, and social conditions from China’s past, blending historical fact with literary imagination to explore cultural, political, and moral themes.
-
E.
Chinese classic
A Chinese classic is a revered traditional text from ancient China that embodies foundational philosophies, literature, history, or cultural values and has exerted lasting influence on Chinese civilization.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:51 a.m.