Triple
T4518001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihai Viteazul |
E103199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Moldavia |
C17082
|
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: ruler of Moldavia Context triple: [Mihai Viteazul, instanceOf, ruler of Moldavia]
-
A.
monarch of Galicia–Volhynia
The monarch of Galicia–Volhynia was the sovereign ruler of the medieval East Slavic kingdom of Galicia–Volhynia, exercising supreme political, military, and judicial authority over its territories and subjects.
-
B.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its armies, and representing it in foreign affairs.
-
C.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its military, and representing it in foreign affairs.
-
D.
Prince of Bulgaria
A Prince of Bulgaria is a male royal titleholder, typically a son or close male relative of the reigning Bulgarian monarch, who holds a defined place in the line of succession and represents the Bulgarian royal family in ceremonial and dynastic roles.
-
E.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions and alliances with neighboring states.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:02 p.m.