Triple
T19238488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gath |
E481065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Philistine city-state |
C35610
|
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: Philistine city-state Context triple: [Gath, instanceOf, Philistine city-state]
-
A.
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.
-
B.
Philistine settlement
chosen
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.
Mesopotamian city
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
D.
Phrygian city
A Phrygian city is an ancient urban settlement located in the historical region of Phrygia in central Anatolia, characterized by its distinctive rock-cut architecture, religious monuments, and role in the Phrygian kingdom’s political and cultural life.
-
E.
Etruscan city
An Etruscan city is an urban center of the ancient Etruscan civilization in central Italy, characterized by fortified hilltop locations, planned street layouts, religious and civic monuments, and a strong regional trade and cultural network.
- 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.