Triple
T21409429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State historic markers |
E528128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic marker program |
C6814
|
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 marker program Context triple: [New York State historic markers, instanceOf, historic marker program]
-
A.
historic sign
chosen
A historic sign is a posted marker or plaque that conveys information about a significant past event, person, place, or structure associated with its location.
-
B.
historic flagpole
A historic flagpole is a vertical structure of notable age or significance that has been preserved or commemorated due to its association with important events, locations, or cultural heritage.
-
C.
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.
-
D.
historic district protection program
A historic district protection program is a coordinated set of policies, regulations, and incentives designed to preserve, maintain, and enhance the architectural, cultural, and historical character of designated areas.
-
E.
historic preservation project
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:41 p.m.