Triple
T29545282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittite queens |
E749613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hittite people |
C35150
|
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: Hittite people Context triple: [Hittite queens, instanceOf, Hittite people]
-
A.
Hittite
chosen
Hittite refers to an ancient Anatolian people and their Indo-European language, prominent in the second millennium BCE and known for establishing a powerful empire centered in Hattusa.
-
B.
Sarmatian people
The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
-
C.
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.
-
D.
Assyrian people
Assyrian people are an indigenous ethnic group of Mesopotamia, primarily Christian, with a distinct Aramaic language and cultural heritage spanning modern-day Iraq, Syria, Turkey, and Iran, as well as a widespread global diaspora.
-
E.
Canaanite people
The Canaanite people were a diverse group of ancient Semitic-speaking communities inhabiting the Levant (particularly modern-day Israel, Palestine, Lebanon, and parts of Syria and Jordan), known for their city-states, polytheistic religion, and significant cultural influence on later Near Eastern civilizations.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:06 p.m.