Triple
T31834773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuangling |
E812640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tang imperial mausoleum |
C59682
|
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: Tang imperial mausoleum Context triple: [Zhuangling, instanceOf, Tang imperial mausoleum]
-
A.
imperial mausoleum ensemble
An imperial mausoleum ensemble is a monumental architectural and landscape complex designed as the burial and commemorative site for an emperor or ruling dynasty, typically integrating tombs, ceremonial structures, and symbolic spatial arrangements.
-
B.
Joseon royal tomb
A Joseon royal tomb is a carefully designed burial site for kings and queens of Korea’s Joseon dynasty, combining Confucian ritual spaces, landscaped mounds, and stone monuments to honor and protect the deceased.
-
C.
Joseon Dynasty royal tomb
A Joseon Dynasty royal tomb is a carefully designed burial site for kings, queens, and royal family members of Korea’s Joseon period, combining Confucian ritual spaces, geomantic principles, and stone sculptures within a landscaped setting.
-
D.
Royal tomb of the Joseon Dynasty
A Royal tomb of the Joseon Dynasty is a monumental burial site constructed for Joseon kings and queens, designed according to Confucian and geomantic principles to honor their authority, virtue, and ancestral legacy.
-
E.
Maya royal tomb
A Maya royal tomb is an elaborately constructed burial chamber for elite rulers, often richly furnished with offerings, inscriptions, and symbolic imagery to ensure the deceased’s status and journey in the afterlife.
- F. None of above. chosen
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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:48 p.m.