Triple
T26078880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Dmitrov |
E657772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary princely title |
C17262
|
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: hereditary princely title Context triple: [Prince of Dmitrov, instanceOf, hereditary princely title]
-
A.
hereditary dukedom
A hereditary dukedom is a noble title and territorial or honorary domain passed down through generations within a family, typically according to established rules of succession.
-
B.
system of hereditary titles
A system of hereditary titles is a structured hierarchy of ranks and honors that are legally or socially passed down through family lines, typically from one generation to the next.
-
C.
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.
-
D.
hereditary consort title
A hereditary consort title is a noble or royal designation traditionally held by the spouse of a reigning or titled individual that can be passed down through generations according to established rules of succession.
-
E.
hereditary principality
chosen
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.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:36 p.m.