Triple
T16085995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Historic Preservation and Archaeology |
E390229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeology agency |
C36956
|
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: archaeology agency Context triple: [Division of Historic Preservation and Archaeology, instanceOf, archaeology agency]
-
A.
archaeology department
An archaeology department is an academic unit dedicated to the systematic study, research, and teaching of past human cultures through the analysis of material remains and related scientific methods.
-
B.
archaeological park authority
An archaeological park authority is an organization responsible for managing, protecting, researching, and presenting archaeological sites and their surrounding landscapes for public benefit and heritage conservation.
-
C.
archaeological research institute
An archaeological research institute is an organization dedicated to the systematic study, excavation, analysis, and preservation of material remains from past human cultures to advance historical and scientific knowledge.
-
D.
archaeological partnership
An archaeological partnership is a collaborative relationship between individuals, institutions, or communities that jointly plan, conduct, and interpret archaeological research while sharing resources, responsibilities, and benefits.
-
E.
archaeological unit
An archaeological unit is a defined three-dimensional segment of an excavation area, recorded and analyzed as a discrete context of past human activity.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 4:59 a.m.