Triple
T4354754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Antebellum Home and Gardens |
E98119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek Revival house |
C8368
|
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: Greek Revival house Context triple: [Arlington Antebellum Home and Gardens, instanceOf, Greek Revival house]
-
A.
Greek Revival building
chosen
A Greek Revival building is a structure designed in the early- to mid-19th-century architectural style that emulates classical Greek temples through features like tall columns, pediments, symmetrical facades, and bold, simple moldings.
-
B.
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.
-
C.
Mediterranean Revival building
A Mediterranean Revival building is an architectural structure characterized by stucco walls, red tile roofs, arches, and ornamental details inspired by Spanish, Italian, and other Mediterranean coastal traditions.
-
D.
Romanesque Revival building
A Romanesque Revival building is a structure designed in a 19th-century historicist style that reinterprets medieval Romanesque architecture through features like round arches, heavy masonry, robust towers, and deeply recessed openings.
-
E.
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.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:16 p.m.