Triple

T28359891
Position Surface form Disambiguated ID Type / Status
Subject Royal Palace ruins (Visegrád) E718335 entity
Predicate instanceOf P0 FINISHED
Object royal residence ruins C38964 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 residence ruins
Context triple: [Royal Palace ruins (Visegrád), instanceOf, royal residence ruins]
  • A. royal palace complex
    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 mausoleum ensemble
    An imperial mausoleum ensemble is a monumental architectural and landscape complex designed as the burial and commemorative site for an emperor or ruling dynasty, typically integrating tombs, ceremonial structures, and symbolic spatial arrangements.
  • C. 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.
  • D. Sasanian palace
    A Sasanian palace is a grand royal complex from the Sasanian Empire, characterized by monumental vaulted halls, domed audience chambers, rich stucco and brick decoration, and a layout designed to express imperial power and ceremonial hierarchy.
  • E. fortified royal residence chosen
    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.
  • 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_69eff6ed5af48190be4e0adf298223e0 completed April 27, 2026, 11:53 p.m.
Created at: April 28, 2026, 12:51 a.m.