Triple
T22716701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huizhou ancestral halls |
E561752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Chinese religious architecture |
C2450
|
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 Chinese religious architecture Context triple: [Huizhou ancestral halls, instanceOf, traditional Chinese religious architecture]
-
A.
Chinese temple
chosen
A Chinese temple is a traditional religious complex designed for worship, ritual, and community gatherings, often featuring ornate roofs, symbolic decorations, and altars dedicated to deities, ancestors, or spiritual figures.
-
B.
temple architecture
Temple architecture is the conceptual class encompassing the design principles, structural elements, symbolic forms, and spatial organization used to create sacred buildings for worship across different cultures and historical periods.
-
C.
Song dynasty architecture
Song dynasty architecture is a Chinese architectural style characterized by refined timber construction, elegant proportional systems, and detailed structural documentation, emphasizing practicality, harmony with nature, and standardized building methods.
-
D.
Ming dynasty architecture
Ming dynasty architecture is a style of Chinese building characterized by strict symmetry, axial layouts, timber-frame construction with bracket sets (dougong), raised platforms, and elaborately decorated roofs with glazed tiles, reflecting imperial authority and Confucian order.
-
E.
유교 사당
유교 사당은 유교의 성현과 조상에게 제사를 지내고 유교적 예절과 도덕을 실천·교육하는 전통 제의 공간이다.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:19 p.m.