Triple
T26772717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary of Anjou |
E670023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 14th-century Hungarian monarch |
C13312
|
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: 14th-century Hungarian monarch Context triple: [Mary of Anjou, instanceOf, 14th-century Hungarian monarch]
-
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
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.
regent of Hungary
A regent of Hungary is a person appointed to govern the Kingdom of Hungary in place of the monarch, typically during a vacancy, minority, or incapacity of the crown.
-
D.
Palatine of Hungary
The Palatine of Hungary was the highest-ranking official after the king in the Kingdom of Hungary, serving as the monarch’s chief representative, judge, and administrator, especially in the king’s absence.
-
E.
14th-century monarch
chosen
A 14th-century monarch is a hereditary or elected sovereign who ruled a kingdom or empire during the 1300s, navigating feudal power structures, dynastic politics, warfare, and shifting religious and economic landscapes.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:03 a.m.