Triple

T6476556
Position Surface form Disambiguated ID Type / Status
Subject Great Hall at Hampton Court Palace E146086 entity
Predicate instanceOf P0 FINISHED
Object Tudor architecture C11069 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: Tudor architecture
Context triple: [Great Hall at Hampton Court Palace, instanceOf, Tudor architecture]
  • A. 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.
  • B. Elizabethan-style theatre
    An Elizabethan-style theatre is a circular or polygonal, open-air playhouse with tiered galleries and a thrust stage projecting into a central yard, designed to host live performances for diverse audiences in the late 16th and early 17th centuries.
  • C. Tudor monarch
    A Tudor monarch is a ruler from the English royal House of Tudor (1485–1603), characterized by strong centralized authority, religious upheaval, and significant cultural and political transformation in England.
  • D. Edwardian Baroque building
    An Edwardian Baroque building is a grand early-20th-century structure characterized by bold classical forms, rich ornamentation, and dramatic massing that reinterpret Baroque motifs within the context of Edwardian-era architecture.
  • E. Gothic building chosen
    A Gothic building is a tall, often stone structure characterized by pointed arches, ribbed vaults, flying buttresses, and large stained-glass windows that create a dramatic, vertically oriented aesthetic.
  • 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_69c008fec7408190af7b146dc63d9750 completed March 22, 2026, 3:21 p.m.
Created at: March 22, 2026, 4:51 p.m.