Triple
T16914591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etruscan League |
E410289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Etruscan political organization |
C37741
|
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: Etruscan political organization Context triple: [Etruscan League, instanceOf, Etruscan political organization]
-
A.
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.
-
B.
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.
-
C.
ancient Anatolian polities
Ancient Anatolian polities were the diverse city-states, kingdoms, and empires that arose in the region of Anatolia (modern-day Turkey), including powers such as the Hittites, Lydians, Phrygians, and others, which played key roles in the political and cultural dynamics of the ancient Near East and Mediterranean.
-
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.
King of Etruria
The King of Etruria was the monarch who ruled the short-lived Kingdom of Etruria (1801–1807) in central Italy under the influence of Napoleonic France.
- F. None of above. chosen
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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.