Triple
T22694064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Highway Historical Marker Program |
E561124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state historical 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: state historical marker program Context triple: [North Carolina Highway Historical Marker Program, instanceOf, state historical marker program]
-
A.
California state historic preservation program
The California state historic preservation program is a government-led initiative that identifies, protects, and promotes the state’s historically and culturally significant buildings, sites, and landscapes through designation, regulation, and public support.
-
B.
living history program
A living history program is an educational experience in which participants reenact or demonstrate past ways of life, events, or practices in an immersive, interactive setting to bring history to life for an audience.
-
C.
state memorial
A state memorial is a formally designated monument, site, or structure established by a government to commemorate significant historical events, individuals, or collective experiences of public importance.
-
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 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.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:14 p.m.