Triple
T18471977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George I Rákóczi |
E451324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Transylvania |
C13121
|
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: prince of Transylvania Context triple: [George I Rákóczi, instanceOf, prince of Transylvania]
-
A.
Prince of Transylvania
chosen
A Prince of Transylvania is the sovereign or semi-sovereign ruler of the historical region of Transylvania, traditionally holding political, military, and often symbolic authority over its territories and people.
-
B.
prince of Wallachia
A prince of Wallachia is the sovereign ruler of the historical principality of Wallachia, responsible for governing its territories, leading its military, and navigating complex regional politics, often under the influence or suzerainty of larger neighboring powers.
-
C.
Duke of Bohemia
The Duke of Bohemia is a noble title historically held by the ruler of the Bohemian duchy, signifying regional authority, aristocratic status, and political influence within the medieval and early modern Holy Roman Empire.
-
D.
Duke of Moravia
The Duke of Moravia is a high-ranking noble ruler who governs the historical region of Moravia, overseeing its political, military, and economic affairs within a broader medieval or feudal realm.
-
E.
Prince of Galicia
A Prince of Galicia is a royal male heir or ruler associated with the historical region of Galicia, holding dynastic authority, territorial rights, and political influence within its medieval or early modern monarchy.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:34 a.m.