Triple
T13704087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Écurie, Versailles |
E328593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of palace complex |
C34066
|
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: component of palace complex Context triple: [Grand Écurie, Versailles, instanceOf, component of palace complex]
-
A.
part of Topkapi Palace
A part of Topkapi Palace represents a distinct architectural or functional section within the historic Ottoman palace complex, such as a courtyard, pavilion, gate, or residential quarter.
-
B.
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.
-
C.
palace and park ensemble
A palace and park ensemble is a unified architectural and landscape complex where a grand residence is integrated with designed gardens, water features, and surrounding grounds to form a cohesive cultural and aesthetic whole.
-
D.
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.
-
E.
section of mausoleum
A section of mausoleum is a distinct, often enclosed subdivision within a larger mausoleum structure, designed to house and organize multiple burial chambers or memorial niches.
- F. None of above. chosen
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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.