Triple
T15889395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amorite dynasty of Qatna |
E385276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern 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 Near Eastern dynasty Context triple: [Amorite dynasty of Qatna, instanceOf, ancient Near Eastern dynasty]
-
A.
Sumerian dynasty
A Sumerian dynasty is a succession of rulers from the same family or lineage who governed a Sumerian city-state or region in ancient Mesopotamia.
-
B.
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.
-
C.
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.
-
D.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
E.
ancient empire
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.