Triple
T32239469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingelheim Imperial Palace |
E823567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian royal palace |
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 royal palace Context triple: [Ingelheim Imperial Palace, instanceOf, Carolingian royal palace]
-
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.
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.
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.
-
D.
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.
-
E.
Baroque palace
A Baroque palace is a grand, ornately decorated residence characterized by dramatic architecture, elaborate ornamentation, and richly detailed interiors designed to display power and opulence.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.