Triple
T5319914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Géza, Grand Prince of the Hungarians |
E121646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Prince of the Hungarians |
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: Grand Prince of the Hungarians Context triple: [Géza, Grand Prince of the Hungarians, instanceOf, Grand Prince of the Hungarians]
-
A.
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.
-
B.
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.
-
C.
King of Croatia
The King of Croatia is the sovereign ruler and highest authority of the Croatian kingdom, responsible for governance, military leadership, and the representation of the realm in domestic and foreign affairs.
-
D.
Polish duke
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
-
E.
Grand Prince of Kiev
The Grand Prince of Kiev was the supreme ruler of Kievan Rus', serving as the principal political, military, and often spiritual leader who held primacy over other regional princes in the federation of East Slavic territories.
- 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.