Triple
T30617514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilgal |
E779353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Israelite site |
C57664
|
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 Israelite site Context triple: [Gilgal, instanceOf, ancient Israelite 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.
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.
-
D.
Early Bronze Age site
An Early Bronze Age site is an archaeological location dating to the early phase of the Bronze Age, characterized by early metalworking, emerging social complexity, and associated settlement or burial remains.
-
E.
Philistine settlement
A Philistine settlement is an archaeological and historical concept referring to a community or town established and inhabited by the Philistines, typically characterized by distinct material culture, architecture, and coastal Levantine location during the Iron Age.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.