Triple
T25614033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huasca de Ocampo haciendas |
E642112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic estate complex ensemble |
C49172
|
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 estate complex ensemble Context triple: [Huasca de Ocampo haciendas, instanceOf, historic estate complex ensemble]
-
A.
historic estate
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 townhouse complex
A historic townhouse complex is a group of architecturally significant, attached or closely spaced residential buildings from a past era, preserved or restored to reflect their original period style and urban context.
-
D.
historic landed estates
chosen
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.
-
E.
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.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:43 p.m.