Triple
T10632151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinson Mounds |
E250482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state archaeological park |
C28770
|
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 archaeological park Context triple: [Pinson Mounds, instanceOf, state archaeological park]
-
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.
historic park system
A historic park system is a coordinated network of parks, landscapes, and related sites preserved and managed to protect, interpret, and provide public access to places of significant historical, cultural, and architectural value.
-
C.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
D.
state recreation site
A state recreation site is a designated public area managed by a state agency that provides natural or developed settings for outdoor leisure activities such as camping, hiking, fishing, and picnicking.
-
E.
United States National Historical Park
A United States National Historical Park is a protected area designated by the federal government to preserve and interpret places of national historical significance, often encompassing multiple sites or a large landscape associated with important events, people, or themes in American history.
- F. None of above. chosen
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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:01 p.m.