Triple
T14930290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberian-Julian dynasty |
E372242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bosporan dynasty |
C33597
|
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: Bosporan dynasty Context triple: [Tiberian-Julian dynasty, instanceOf, Bosporan dynasty]
-
A.
Bosporan king
chosen
A Bosporan king is the monarch who ruled the ancient Bosporan Kingdom around the Black Sea, wielding political, military, and economic authority over its diverse Hellenistic and local populations.
-
B.
Sarmatian people
The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
-
C.
Nabataean dynasty
The Nabataean dynasty was an ancient Arab royal house that ruled the Nabataean Kingdom, centered on Petra, from around the 3rd century BCE until its annexation by the Roman Empire in 106 CE.
-
D.
Bulgar state
A Bulgar state is a political entity historically founded and ruled by the Bulgar people, typically characterized by a semi-nomadic warrior elite governing settled agricultural populations within a defined territory.
-
E.
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.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:36 a.m.