Triple

T36433084
Position Surface form Disambiguated ID Type / Status
Subject Carolingian court at Quierzy E897496 entity
Predicate instanceOf P0 FINISHED
Object Carolingian palace complex C27127 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: Carolingian palace complex
Context triple: [Carolingian court at Quierzy, instanceOf, Carolingian palace complex]
  • A. 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.
  • B. Carolingian architecture chosen
    Carolingian architecture is a style of early medieval European building, promoted by the Carolingian dynasty (8th–9th centuries), that revived and adapted elements of ancient Roman and early Christian architecture to express imperial power and religious reform.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69f76e56636481908eda808ab0273401 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.