Triple
T32826718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurumbranad |
E839573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former princely chieftaincy |
C53345
|
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: former princely chieftaincy Context triple: [Kurumbranad, instanceOf, former princely chieftaincy]
-
A.
princely office
A princely office is an institutional role or position held by a prince or princely figure, encompassing the authority, duties, and ceremonial functions associated with governing or representing a principality or royal domain.
-
B.
local chieftaincy institution
chosen
A local chieftaincy institution is a traditional governance structure led by a recognized chief or council of chiefs that exercises cultural, social, and sometimes political authority within a specific community or territory.
-
C.
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.
-
D.
feudatory ruler
A feudatory ruler is a subordinate sovereign who governs a territory and owes allegiance, tribute, and military support to a more powerful overlord or suzerain.
-
E.
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.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.