Triple
T31882079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level III (Assyrian destruction level) |
E813908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological layer |
C45611
|
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 layer Context triple: [Level III (Assyrian destruction level), instanceOf, archaeological layer]
-
A.
archaeological deposit
chosen
An archaeological deposit is a distinct layer or accumulation of material remains and sediments formed by past human activity and natural processes, preserved in the ground for study.
-
B.
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.
-
C.
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.
-
D.
archaeological locality
An archaeological locality is a specific geographic area where evidence of past human activity, such as artifacts, features, or structures, is found and studied in its environmental context.
-
E.
archaeological culture
An archaeological culture is a recurring assemblage of artifacts, features, and other material remains that archaeologists interpret as representing the activities and shared practices of a particular group of people in a specific time and place.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:56 p.m.