Triple
T3257218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmarks in New York |
E68325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage designation category |
C826
|
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 designation category Context triple: [National Historic Landmarks in New York, instanceOf, heritage designation category]
-
A.
cultural heritage designation
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
-
B.
historic designation
chosen
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.
-
C.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
D.
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.
-
E.
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.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:09 p.m.