Triple
T36173202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagebrush House |
E1046502
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site in the United States |
C11600
|
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: archaeological site in the United States Context triple: [Sagebrush House, instanceOf, archaeological site in the United States]
-
A.
archaeological site in Mexico
An archaeological site in Mexico is a location where physical remains of past human activity—such as structures, artifacts, and cultural features—have been preserved and studied to understand the region’s historical and pre-Hispanic civilizations.
-
B.
United States national battlefield
A United States national battlefield is a protected area designated by the federal government to preserve and interpret the site of a significant historic battle, typically from the American Civil War, for public education and commemoration.
-
C.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
D.
state archaeological park
A state archaeological park is a protected area managed by a state government that preserves, studies, and interprets significant archaeological sites and artifacts for public education and enjoyment.
-
E.
prehistoric archaeological site complex
A prehistoric archaeological site complex is an interconnected group of ancient locations containing material remains and features that together reveal patterns of human activity, settlement, and culture before written history.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.