Triple
T13820301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bliss and Dickie |
E332116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological partnership |
C34225
|
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 partnership Context triple: [Bliss and Dickie, instanceOf, archaeological partnership]
-
A.
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.
-
B.
archaeological component
An archaeological component is a distinct, temporally and functionally coherent set of artifacts, features, and other cultural materials at a site that represents a specific episode or phase of past human activity.
-
C.
archaeological site collection
An archaeological site collection is an organized assemblage of artifacts, ecofacts, records, and related materials systematically gathered from one or more archaeological sites for study, preservation, and interpretation.
-
D.
archaeological site network
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
-
E.
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.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.