Triple
T35766592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åråsen farm area |
E1034031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic agricultural estate |
C3229
|
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 agricultural estate Context triple: [Åråsen farm area, instanceOf, historic agricultural estate]
-
A.
historic farmstead
chosen
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
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
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 communal farm
A historic communal farm is a shared agricultural property where a community of people collectively lived and worked the land, reflecting past social, economic, and cultural practices of cooperative rural life.
-
E.
historic garden
A historic garden is a designed outdoor space of recognized cultural, aesthetic, or historical significance, preserved or restored to reflect the landscape styles, plantings, and features of a particular period or tradition.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.