Triple
T3788851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkhangelskoye Estate |
E89595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | palace-and-park complex |
C12406
|
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: palace-and-park complex Context triple: [Arkhangelskoye Estate, instanceOf, palace-and-park complex]
-
A.
palace and park ensemble
chosen
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.
-
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.
royal stables complex
A royal stables complex is an organized ensemble of buildings and yards designed to house, train, and maintain horses and related equipment for a royal household’s transportation, ceremonial, and military needs.
-
D.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
E.
museum building complex
A museum building complex is a coordinated group of structures and spaces designed to collect, preserve, exhibit, and interpret cultural, historical, artistic, or scientific artifacts for public education and enjoyment.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:14 p.m.