Triple
T11505713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholasville (Nicholas family / likely Colonel George Nicholas) |
E272777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic property name |
C30125
|
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 property name Context triple: [Nicholasville (Nicholas family / likely Colonel George Nicholas), instanceOf, historic property name]
-
A.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
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 district contributing property
A historic district contributing property is a building, structure, site, or object within a designated historic district that adds to the district’s historical, architectural, or cultural significance.
-
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 hotel
A historic hotel is a lodging establishment of notable age and preserved architectural or cultural significance that offers accommodations while reflecting the heritage of its era.
- F. None of above. chosen
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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:36 p.m.