Triple
T29312481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | country estate Rinderweid |
E743277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic rural property |
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 rural property Context triple: [country estate Rinderweid, instanceOf, historic rural property]
-
A.
historic farmstead
A historic farmstead is a preserved agricultural property, including its farmhouse, outbuildings, fields, and landscape features, that collectively illustrate the farming practices, architecture, and rural life of a particular period in history.
-
B.
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.
-
C.
historic barn
A historic barn is an old agricultural building of significant age and cultural, architectural, or historical value, often preserved as a heritage structure reflecting past farming practices and rural life.
-
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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:17 p.m.