Triple
T7359072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravensworth, Fairfax County, Virginia |
E169699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic plantation estate |
C17952
|
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 plantation estate Context triple: [Ravensworth, Fairfax County, Virginia, instanceOf, historic plantation estate]
-
A.
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.
-
B.
colonial-era plantation
chosen
A colonial-era plantation is a large agricultural estate established during the colonial period that relied on coerced or enslaved labor to produce cash crops for export, typically reinforcing systems of racial and economic exploitation.
-
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 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.
-
E.
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.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:06 p.m.