Triple
T8397279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menua |
E198085
|
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: [Menua, instanceOf, Ancient Near Eastern ruler]
-
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.
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.
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.
-
D.
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.
-
E.
Hittite king
A Hittite king is the supreme political, military, and religious ruler of the Hittite Empire, responsible for governing the state, leading armies, conducting diplomacy, and performing key religious rituals to maintain divine favor and social order.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:04 p.m.