Triple
T5593938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRHR |
E146948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | California state heritage register |
C6836
|
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: California state heritage register Context triple: [CRHR, instanceOf, California state heritage register]
-
A.
California State Historic Park
A California State Historic Park is a protected area in California designated to preserve and interpret sites, structures, and landscapes of significant historical and cultural importance to the state.
-
B.
State Heritage Area
chosen
A State Heritage Area is a geographically defined place recognized and protected by a state government for its outstanding cultural, historical, or natural significance.
-
C.
National Register of Historic Places listings
National Register of Historic Places listings are official records of buildings, sites, structures, districts, and objects recognized by the United States federal government as worthy of preservation for their historical, architectural, archaeological, or cultural significance.
-
D.
National Heritage Area
A National Heritage Area is a region designated by the U.S. Congress where natural, cultural, and historic resources form a cohesive, nationally important landscape managed through partnerships rather than federal land ownership.
-
E.
New York State Historic Site
A New York State Historic Site is a location officially designated and managed by New York State for its significant historical, cultural, or architectural importance.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:38 p.m.