Triple
T33248923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream of the Red Chamber |
E851183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty literature |
C54507
|
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: Qing dynasty literature Context triple: [Dream of the Red Chamber, instanceOf, Qing dynasty literature]
-
A.
Qing dynasty document
chosen
A Qing dynasty document is an official or private written record produced under the Qing imperial rule (1644–1912), reflecting the administrative, legal, cultural, or social practices of that period.
-
B.
Song dynasty text
A Song dynasty text is a written work produced or compiled during China’s Song dynasty (960–1279), reflecting its era’s distinctive intellectual, literary, religious, and bureaucratic developments.
-
C.
Tang dynasty poetry
Tang dynasty poetry is a body of Chinese verse from the Tang era (618–907) renowned for its refined language, rich imagery, and diverse themes ranging from nature and friendship to politics and personal reflection.
-
D.
Qing dynasty structure
A Qing dynasty structure is a building or architectural element constructed or styled during China’s Qing dynasty (1644–1912), typically featuring timber frameworks, bracket sets, sweeping roofs, and ornate decorative details reflecting imperial and regional aesthetics.
-
E.
Yuan dynasty court
The Yuan dynasty court was the central governing institution of the Mongol-ruled Chinese empire, where the emperor and his officials conducted political, military, and ceremonial affairs that integrated Mongol and Chinese traditions.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.