Triple
T23377560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deir Alla archaeological site |
E593647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern site |
C35265
|
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: ancient Near Eastern site Context triple: [Deir Alla archaeological site, instanceOf, ancient Near Eastern site]
-
A.
neolithic site
A neolithic site is an archaeological location containing material remains and features from the New Stone Age, reflecting early farming communities, permanent settlements, and the development of complex social and technological practices.
-
B.
ancient Nubian site
An ancient Nubian site is an archaeological location in the Nile Valley region of Nubia that preserves the material remains, architecture, and cultural landscapes of the historic Nubian civilizations.
-
C.
Urartian archaeological site
An Urartian archaeological site is a location containing the material remains—such as fortresses, temples, settlements, and artifacts—of the Iron Age kingdom of Urartu, offering evidence of its political, economic, and religious life.
-
D.
ancient village site
An ancient village site is an archaeological location preserving the remains of a past community’s dwellings, activity areas, and material culture, offering evidence of its social, economic, and environmental history.
-
E.
ancient place
chosen
An ancient place is a historically significant location from antiquity, often associated with early civilizations, archaeological remains, or long-standing cultural traditions.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:33 p.m.