Triple
T23128988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashur-nadin-shumi |
E577115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Neo-Assyrian prince |
C47263
|
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: Neo-Assyrian prince Context triple: [Ashur-nadin-shumi, instanceOf, Neo-Assyrian prince]
-
A.
Neo-Babylonian prince
A Neo-Babylonian prince is a royal male heir or close relative of the king in the Neo-Babylonian Empire (c. 626–539 BCE), raised within the courtly, military, and religious traditions that prepared him for governance and dynastic continuity.
-
B.
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.
-
C.
Nabatean prince
A Nabatean prince is a royal male member of the ancient Nabatean kingdom’s ruling family, typically involved in governance, diplomacy, and the management of trade and territorial affairs.
-
D.
Palmyrene prince
A Palmyrene prince is a male member of the royal or ruling elite of the ancient city-state of Palmyra in Roman Syria, often involved in governance, military leadership, and regional diplomacy.
-
E.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4 p.m.