Triple
T22556188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongsseteren |
E557688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal lodge |
C37154
|
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 lodge Context triple: [Kongsseteren, instanceOf, royal lodge]
-
A.
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.
-
B.
royal retreat
chosen
A royal retreat is an exclusive, often secluded residence or estate where members of a royal family withdraw from public duties to rest, reflect, and conduct private affairs in a luxurious and secure setting.
-
C.
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.
-
D.
Tudor palace
A Tudor palace is a grand, often asymmetrical royal or noble residence from England’s Tudor period, characterized by red-brick construction, ornate chimneys, timber framing, and richly decorated interiors reflecting both medieval and early Renaissance influences.
-
E.
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.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:52 p.m.