Triple
T3556438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biltmore Dairy Barn |
E75230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic agricultural building |
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 building Context triple: [Biltmore Dairy Barn, instanceOf, historic agricultural building]
-
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 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.
-
D.
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.
-
E.
historic gristmill
A historic gristmill is a traditional milling facility, often water- or wind-powered, where grain was ground into flour and which now serves as a preserved example of early industrial and agricultural technology.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:20 p.m.