Triple
T14123074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stables (Christiansborg Palace) |
E339950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal stables |
C13357
|
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 stables Context triple: [Royal Stables (Christiansborg Palace), instanceOf, royal stables]
-
A.
royal stables complex
chosen
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.
-
B.
royal hunting estate
A royal hunting estate is a large, often secluded tract of land reserved for a monarch and their court, combining managed wilderness, game populations, and supporting facilities for exclusive hunting, leisure, and display of power.
-
C.
royal monastery
A royal monastery is a religious institution founded, patronized, or closely associated with a ruling monarch or royal family, serving both spiritual functions and dynastic or state interests.
-
D.
royal pavilion
A royal pavilion is an ornate, often temporary or semi-permanent structure used by royalty for ceremonial, recreational, or representational purposes, typically featuring luxurious design and prominent placement within palace grounds or formal landscapes.
-
E.
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.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.