Triple
T5319915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Géza, Grand Prince of the Hungarians |
E121646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian ruler |
C5719
|
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: Hungarian ruler Context triple: [Géza, Grand Prince of the Hungarians, instanceOf, Hungarian ruler]
-
A.
Hungarian monarch
chosen
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
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.
Eastern European monarch
An Eastern European monarch is a sovereign ruler—such as a king, queen, tsar, or grand duke—who governs or ceremonially represents a state in the Eastern European region, shaped by its distinct historical, cultural, and political traditions.
-
E.
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.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.