Triple
T30968671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abisare |
E789029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | king of Larsa |
C59104
|
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: king of Larsa Context triple: [Abisare, instanceOf, king of Larsa]
-
A.
Amorite king
An Amorite king is a Bronze Age ruler from the Amorite people of ancient Mesopotamia, governing city-states or kingdoms such as Babylon through military power, diplomacy, and religious authority.
-
B.
Mitanni king
A Mitanni king was the sovereign ruler of the ancient Hurrian-speaking kingdom of Mitanni in northern Mesopotamia and Syria during the mid–second millennium BCE, overseeing its political, military, and religious affairs.
-
C.
King of Mari
The King of Mari is the sovereign ruler of the ancient Mesopotamian city-state of Mari, responsible for governing its people, overseeing religious and military affairs, and managing diplomatic relations with neighboring powers.
-
D.
Kassite king
A Kassite king was the sovereign ruler of Babylonia during the Kassite dynasty (c. 16th–12th centuries BCE), overseeing political authority, military campaigns, religious patronage, and the administration of land and resources.
-
E.
King of Urartu
The King of Urartu is the sovereign ruler of the ancient kingdom of Urartu, responsible for governing its territories, commanding its military, overseeing religious and administrative affairs, and representing the state in foreign relations.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.