Triple
T34228621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aranjuez Cultural Landscape |
E878128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic royal estate |
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 royal estate Context triple: [Aranjuez Cultural Landscape, instanceOf, historic royal estate]
-
A.
historic palace
A historic palace is a grand, architecturally significant residence once occupied by royalty or nobility, preserved as a cultural landmark that reflects the political, social, and artistic heritage of its era.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
historic retreat
A historic retreat is a tranquil getaway destination centered around preserved or restored heritage properties, offering guests immersive experiences in the culture, architecture, and stories of the past.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.