Triple
T4517999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihai Viteazul |
E103199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Wallachia |
C17081
|
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 Wallachia Context triple: [Mihai Viteazul, instanceOf, prince of Wallachia]
-
A.
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.
-
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.
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.
-
D.
Tsar of Bulgaria
The Tsar of Bulgaria was the monarchic ruler of the Bulgarian state, holding supreme political and often religious authority over the country during its medieval and modern imperial periods.
-
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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:02 p.m.