Triple
T15469162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Tyre |
E372111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Phoenician polity |
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: Phoenician polity Context triple: [Kingdom of Tyre, instanceOf, Phoenician polity]
-
A.
Phoenician colony
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.
Arabian polity
An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
-
C.
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.
-
D.
Elamite polity
An Elamite polity is a socio-political entity of ancient Elam, characterized by its own governing structures, territorial domain, and cultural identity within the broader Elamite civilization.
-
E.
Carthaginian dynasty
The Carthaginian dynasty refers to the ruling families and political elites of ancient Carthage who governed the city-state and its territories through a combination of oligarchic councils, powerful merchant-aristocrats, and occasionally dominant ruling houses such as that of Hamilcar Barca.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:33 a.m.