Triple
T19236890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thebez |
E481022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canaanite settlement |
C13065
|
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: Canaanite settlement Context triple: [Thebez, instanceOf, Canaanite settlement]
-
A.
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.
-
B.
Nubian settlement
A Nubian settlement is a community or village inhabited by Nubian people, characterized by distinctive architectural styles, social organization, and cultural practices shaped by the Nile Valley environment and long-standing regional traditions.
-
C.
Nabataean settlement
A Nabataean settlement is an ancient community site established by the Nabataean civilization, typically characterized by rock-cut architecture, sophisticated water management systems, and strategic placement along trade routes in the Near East.
-
D.
Canaanite city-state
chosen
A Canaanite city-state is an independent, fortified urban center in ancient Canaan that controlled its surrounding territory, governed by a local ruler and integrated into regional trade, diplomacy, and warfare.
-
E.
Greco-Roman settlement
A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:26 p.m.