Triple
T1568140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Calvert Historical and Archaeological Park |
E33478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical park |
C2680
|
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: historical park Context triple: [Mount Calvert Historical and Archaeological Park, instanceOf, historical park]
-
A.
historic park
chosen
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.
-
B.
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.
-
C.
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.
-
D.
historic site visitor facility
A historic site visitor facility is a dedicated space that provides services, information, and amenities to support and enhance visitors’ experiences at a historic site.
-
E.
outdoor museum
An outdoor museum is an open-air cultural space where historical artifacts, artworks, or reconstructed buildings are displayed in a natural or urban outdoor setting for public education and enjoyment.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.