Triple
T5161252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Register of Historic Places in Chemung County, New York |
E116441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage register subset |
C12523
|
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: heritage register subset Context triple: [National Register of Historic Places in Chemung County, New York, instanceOf, heritage register subset]
-
A.
heritage register entry
A heritage register entry is an official record documenting the identification, significance, legal status, and key attributes of a place, object, or tradition recognized for its cultural or historical heritage value.
-
B.
heritage centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
-
C.
heritage estate
A heritage estate is a historically significant property, often including land, buildings, and cultural features, preserved for its architectural, cultural, or ancestral value.
-
D.
cultural heritage database
chosen
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
E.
historic environment service
A historic environment service is an organization or unit that identifies, protects, manages, and promotes understanding of historic buildings, archaeological sites, and cultural landscapes within a given area.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:44 p.m.