Triple
T23750532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genovia |
E586951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional European principality |
C22346
|
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: fictional European principality Context triple: [Genovia, instanceOf, fictional European principality]
-
A.
hereditary principality
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
B.
Grand Duchy
A Grand Duchy is a sovereign or semi-sovereign state or territory ruled by a grand duke or grand duchess, ranking below a kingdom but above a duchy in traditional European nobility hierarchies.
-
C.
Piast-ruled principality
A Piast-ruled principality is a medieval territorial polity in Central Europe governed by a member of the Piast dynasty, typically characterized by fragmented authority, hereditary rule, and integration into the broader political landscape of the Polish and neighboring realms.
-
D.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
E.
fictional monarchy
chosen
A fictional monarchy is an imagined system of government in which a royal family or single sovereign rules a realm, often shaped by invented histories, cultures, and political dynamics.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:13 p.m.