Triple
T16124666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladislaus II of Bohemia and Hungary |
E391236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monarch of Hungary |
C6183
|
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: monarch of Hungary Context triple: [Vladislaus II of Bohemia and Hungary, instanceOf, monarch of Hungary]
-
A.
Hungarian monarch
A Hungarian monarch is the sovereign ruler of the Kingdom of Hungary, historically holding supreme political, military, and often religious authority over the realm and its subjects.
-
B.
King of Hungary
chosen
The King of Hungary was the sovereign ruler of the Kingdom of Hungary, holding supreme political, military, and often religious authority over its territories and people throughout its monarchical history.
-
C.
Habsburg monarch
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
D.
Emperor of Austria
The Emperor of Austria was the hereditary sovereign of the Austrian Empire (and later the Austro-Hungarian Empire), holding supreme political and symbolic authority over its diverse territories and peoples from 1804 to 1918.
-
E.
monarch of Bohemia
A monarch of Bohemia is the sovereign ruler—historically a duke or king—who held supreme political authority over the region of Bohemia within Central Europe.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.