Triple
T29546008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozia |
E749631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Phoenician settlement |
C6008
|
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: Phoenician settlement Context triple: [Mozia, instanceOf, Phoenician settlement]
-
A.
Phoenician colony
chosen
A Phoenician colony is a settlement established by the ancient maritime Phoenician civilization along foreign coasts for trade, resource extraction, and cultural expansion while maintaining ties to its founding city.
-
B.
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.
-
C.
Minoan settlement
A Minoan settlement is a Bronze Age Cretan habitation site characterized by clustered domestic, religious, and sometimes administrative structures that reflect the social, economic, and cultural organization of Minoan society.
-
D.
Canaanite city-state
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.
Ligurian settlement
A Ligurian settlement is a historically or archaeologically identified inhabited place established or predominantly occupied by the ancient Ligurian people, characterized by their distinct cultural, social, and territorial attributes.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:07 p.m.