Triple
T25619785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schloss Köpenick |
E642262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterside palace |
C24860
|
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: waterside palace Context triple: [Schloss Köpenick, instanceOf, waterside palace]
-
A.
water palace
chosen
A water palace is a grand, often ornate residence or complex built in, on, or surrounded by water, designed to integrate architecture with aquatic features for aesthetic, ceremonial, or recreational purposes.
-
B.
Herrscherhaus
Herrscherhaus is a conceptual class representing a ruling dynasty or sovereign household that embodies political authority, hereditary succession, and the social, cultural, and symbolic structures surrounding monarchical power.
-
C.
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.
-
D.
royal pavilion
A royal pavilion is an ornate, often temporary or semi-permanent structure used by royalty for ceremonial, recreational, or representational purposes, typically featuring luxurious design and prominent placement within palace grounds or formal landscapes.
-
E.
Tudor palace
A Tudor palace is a grand, often asymmetrical royal or noble residence from England’s Tudor period, characterized by red-brick construction, ornate chimneys, timber framing, and richly decorated interiors reflecting both medieval and early Renaissance influences.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:03 p.m.