Triple
T21207676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taksony, Grand Prince of the Hungarians |
E522631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian grand prince |
C33510
|
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 grand prince Context triple: [Taksony, Grand Prince of the Hungarians, instanceOf, Hungarian grand prince]
-
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
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.
Hungarian chieftain
chosen
A Hungarian chieftain is a tribal leader of the early Magyars who held military, political, and social authority over a clan or tribal confederation in the Carpathian Basin during the 9th–10th centuries.
-
D.
Hungarian noble
A Hungarian noble is a member of the historical aristocratic class of the Kingdom of Hungary, holding hereditary titles, land, and political privileges within the kingdom’s feudal and later constitutional systems.
-
E.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:24 p.m.