Triple
T3386046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of the Bosporus |
E71304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greco-Scythian state |
C4291
|
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: Greco-Scythian state Context triple: [Kingdom of the Bosporus, instanceOf, Greco-Scythian state]
-
A.
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.
-
B.
ancient Greek alliance
An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
-
C.
ancient kingdom
chosen
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.
-
D.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
E.
Latin state in Greece
A Latin state in Greece was a feudal polity established by Western European (Latin) crusaders on former Byzantine territory in Greece following the Fourth Crusade, characterized by Latin Christian rule, Western feudal institutions, and cultural interaction with the local Greek population.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:14 p.m.