Triple
T17551872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tudor Village (Hever Castle) |
E427484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mock-Tudor style building complex |
C399
|
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: mock-Tudor style building complex Context triple: [Tudor Village (Hever Castle), instanceOf, mock-Tudor style building complex]
-
A.
masonry structure complex
A masonry structure complex is a group of interconnected or related buildings, walls, and other constructed elements primarily made of stone, brick, or concrete masonry units that function together as a unified built environment.
-
B.
mock castle
A mock castle is a decorative or playful structure designed to resemble a traditional fortress or castle, often used for entertainment, educational, or aesthetic purposes rather than defense.
-
C.
Renaissance building
A Renaissance building is a structure characterized by symmetry, proportion, and classical elements such as columns, pilasters, arches, and domes, reflecting the revival of ancient Greek and Roman architectural principles during the 14th–17th centuries.
-
D.
building complex
chosen
A building complex is a group of interconnected or related structures on a shared site that function together as a unified facility or environment.
-
E.
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.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.