Triple
T16130237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleg Sviatoslavich |
E391376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Chernigov |
C37020
|
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: Prince of Chernigov Context triple: [Oleg Sviatoslavich, instanceOf, Prince of Chernigov]
-
A.
Prince of Volhynia
A Prince of Volhynia was a medieval ruler of the Volhynia principality in the historical region of Ruthenia, exercising political, military, and administrative authority over its territories and people.
-
B.
Prince of Transylvania
A Prince of Transylvania is the sovereign or semi-sovereign ruler of the historical region of Transylvania, traditionally holding political, military, and often symbolic authority over its territories and people.
-
C.
Prince of Galicia
A Prince of Galicia is a royal male heir or ruler associated with the historical region of Galicia, holding dynastic authority, territorial rights, and political influence within its medieval or early modern monarchy.
-
D.
Lord of Milan
A Lord of Milan is a noble ruler who holds political, military, and often economic authority over the city and surrounding territories of Milan during a given historical period.
-
E.
Grand Prince of Moscow
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:01 a.m.