Triple
T31498752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emesene dynasty |
E803618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Syrian dynasty |
C36619
|
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 Syrian dynasty Context triple: [Emesene dynasty, instanceOf, ancient Syrian dynasty]
-
A.
Assyrian dynasty
An Assyrian dynasty is a ruling lineage or succession of kings that governed the Assyrian state or empire during a distinct historical period in ancient Mesopotamia.
-
B.
ancient Near Eastern dynasty
chosen
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.
-
C.
Amorite dynasty
The Amorite dynasty refers to the line of rulers of Amorite origin who established and governed powerful city-states and kingdoms in ancient Mesopotamia, most notably the First Babylonian Dynasty under Hammurabi.
-
D.
ancient Lydian dynasty
The ancient Lydian dynasty refers to the line of kings who ruled the kingdom of Lydia in western Anatolia, most notably the Mermnad dynasty (c. 7th–6th centuries BCE), famed for its wealth, early coinage, and interactions with Greek and Persian powers.
-
E.
Neo-Assyrian dynasty
The Neo-Assyrian dynasty was the ruling line of kings that governed the Neo-Assyrian Empire (c. 911–609 BCE), overseeing its expansion into the dominant military and political power of the ancient Near East.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:43 p.m.