Triple
T13817993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Residential Palace |
E332066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient royal residence |
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: ancient royal residence Context triple: [Residential Palace, instanceOf, ancient royal residence]
-
A.
former royal residence
A former royal residence is a historic building or estate that once served as an official home for a monarch or royal family but no longer functions in that capacity.
-
B.
Byzantine imperial palace
A Byzantine imperial palace is a grand, fortified residential and ceremonial complex that housed the emperor and court, combining administrative, religious, and domestic functions in richly decorated architectural spaces.
-
C.
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.
-
D.
Roman imperial residence
A Roman imperial residence is a grand, often fortified palace complex that served as the official home, administrative center, and ceremonial stage for the Roman emperor and his court.
-
E.
ceremonial palace
A ceremonial palace is a grand, often architecturally elaborate residence or complex designed primarily for hosting formal state rituals, official receptions, and symbolic public events.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.