Triple
T33745073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Court (Royal Palace, Phnom Penh) |
E864676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal residential compound |
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: royal residential compound Context triple: [Inner Court (Royal Palace, Phnom Penh), instanceOf, royal residential compound]
-
A.
royal dwelling
A royal dwelling is a grand, often historically significant residence designed to house a monarch or ruling family, serving both as a private home and a symbol of political power and cultural prestige.
-
B.
fortified royal residence
A fortified royal residence is a heavily defended, often grand architectural complex that serves both as the sovereign’s primary dwelling and as a stronghold for protecting the ruler, court, and seat of power.
-
C.
residential palace building
A residential palace building is a grand, often historically or culturally significant dwelling designed to house royalty, nobility, or other high-status residents, featuring luxurious architecture, expansive interiors, and formal reception spaces.
-
D.
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.
-
E.
royal retreat
A royal retreat is an exclusive, often secluded residence or estate where members of a royal family withdraw from public duties to rest, reflect, and conduct private affairs in a luxurious and secure setting.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.