Triple
T12817393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carian culture |
E306436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anatolian culture |
C7663
|
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: Anatolian culture Context triple: [Carian culture, instanceOf, Anatolian culture]
-
A.
Anatolian language
An Anatolian language is any member of an extinct branch of the Indo-European language family once spoken in ancient Anatolia (modern-day Turkey), including languages such as Hittite, Luwian, and Lycian.
-
B.
ancient Anatolian polities
chosen
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.
-
C.
Roman-era Cappadocian
A Roman-era Cappadocian is an inhabitant of the Cappadocia region during the period of Roman rule, shaped by a blend of local Anatolian traditions and Roman imperial culture, administration, and economy.
-
D.
Hittite institution
A Hittite institution is an organized social, political, religious, or legal structure within Hittite society that governed behavior, administration, and cultural practices in the Hittite civilization.
-
E.
Mycenaean settlement
A Mycenaean settlement is a Late Bronze Age Aegean habitation site characterized by fortified architecture, palatial or administrative centers, and associated domestic, economic, and ritual structures reflecting Mycenaean social and political organization.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:31 p.m.