Triple
T8377890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punic people |
E197620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carthaginian civilization |
C18070
|
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: Carthaginian civilization Context triple: [Punic people, instanceOf, Carthaginian civilization]
-
A.
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.
-
B.
Carthaginian institution
chosen
A Carthaginian institution is a formal or informal organizational structure, practice, or system that governed the political, economic, religious, or social life of ancient Carthage.
-
C.
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.
-
D.
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.
-
E.
ancient Carthaginian person
An ancient Carthaginian person is an individual who lived in or originated from the city-state of Carthage or its territories during antiquity, participating in its Punic culture, society, and historical events.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:02 p.m.