Triple
T32688635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quex Park |
E835795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic house estate |
C1852
|
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: historic house estate Context triple: [Quex Park, instanceOf, historic house estate]
-
A.
historic estate
chosen
A historic estate is a large, significant property—often including a grand residence, outbuildings, and landscaped grounds—that holds cultural, architectural, or historical importance from a past era.
-
B.
historic estate type
A historic estate type is a classification of large, historically significant residential properties characterized by their architectural style, period of construction, original function, and cultural or social importance.
-
C.
Historic house
A historic house is a residential building recognized for its significant architectural, cultural, or historical value, often preserved or restored to reflect the period in which it was built.
-
D.
historic ruined country house
A historic ruined country house is a once-grand rural residence now partially or wholly decayed, whose surviving architecture and setting evoke its former status, period style, and the passage of time.
-
E.
historic landed estates
Historic landed estates are large, traditionally inherited properties comprising extensive landholdings, grand residences, and associated economic, social, and cultural structures that reflect the power and legacy of longstanding landowning families or institutions.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.