Triple
T30618465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Kent County Courthouse Historic District |
E779376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | courthouse historic district |
C24185
|
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: courthouse historic district Context triple: [New Kent County Courthouse Historic District, instanceOf, courthouse historic district]
-
A.
historical district
chosen
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
B.
reconstructed historic district
A reconstructed historic district is an area where buildings, streetscapes, and public spaces have been rebuilt or extensively restored to replicate their historical appearance and character, often based on archival research and archaeological evidence.
-
C.
courthouse
A courthouse is a public building where legal cases are heard and decided, housing courtrooms, judges' chambers, and related judicial offices.
-
D.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
E.
commercial historic district
A commercial historic district is a geographically defined area containing a concentration of historically significant commercial buildings and streetscapes that reflect the economic and cultural development of a community over time.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.