Triple
T8266076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suppiluliuma I |
E193304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern ruler |
C24141
|
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: ancient Near Eastern ruler Context triple: [Suppiluliuma I, instanceOf, ancient Near Eastern ruler]
-
A.
Neo-Assyrian king
A Neo-Assyrian king is the supreme monarch of the Neo-Assyrian Empire, wielding absolute political, military, and religious authority to expand and maintain imperial power across the ancient Near East.
-
B.
ancient Greek ruler
An ancient Greek ruler is a sovereign leader who governed a Greek city-state or kingdom, wielding political, military, and often religious authority within the context of classical Hellenic civilization.
-
C.
Kayanian king
A Kayanian king is the sovereign ruler of the ancient Kayanian dynasty, embodying divine authority, martial prowess, and the cultural ideals of his realm.
-
D.
Neo-Babylonian king
A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
-
E.
Achaemenid ruler
An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:50 p.m.