Triple
T28535883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Hittites |
E722161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern royal office |
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 royal office Context triple: [King of the Hittites, instanceOf, ancient Near Eastern royal office]
-
A.
ancient Near Eastern ruler
chosen
An ancient Near Eastern ruler is a sovereign leader who governed a city-state or empire in regions such as Mesopotamia, Anatolia, the Levant, or Persia, wielding political, military, economic, and often religious authority.
-
B.
royal administration apparatus
The royal administration apparatus is the organized system of offices, officials, and procedures through which a monarchy governs, manages resources, and enforces its authority over a realm.
-
C.
Mesopotamian royal epithet
A Mesopotamian royal epithet is a formal, often formulaic honorific phrase used in inscriptions and texts to define, praise, and legitimize a king’s divine favor, authority, and achievements.
-
D.
ancient Near Eastern dynasty
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
E.
ancient Near Eastern art
Ancient Near Eastern art encompasses the visual and material creations of early civilizations in Mesopotamia, Anatolia, the Levant, and Persia, reflecting their religious beliefs, political power, and daily life through sculpture, reliefs, architecture, and decorative objects.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:32 a.m.