Triple
T3161328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zijincheng |
E66107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial palace complex |
C9043
|
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: imperial palace complex Context triple: [Zijincheng, instanceOf, imperial palace complex]
-
A.
royal palace complex
chosen
A royal palace complex is an expansive, architecturally unified ensemble of residences, ceremonial halls, administrative buildings, gardens, and supporting structures that together serve as the political, cultural, and domestic center of a monarchy.
-
B.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
C.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
D.
imperial durbar
An imperial durbar is a formal ceremonial assembly held by a sovereign or colonial ruler to display imperial authority, receive homage, and conduct state rituals before gathered dignitaries and subjects.
-
E.
wooden palace
A wooden palace is a grand, ornately designed residence or ceremonial building constructed primarily from timber, showcasing intricate craftsmanship and often reflecting the cultural and historical aesthetics of its region.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:05 p.m.