Triple
T14808005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pereyaslavl line |
E348090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval princely line |
C12651
|
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: medieval princely line Context triple: [Pereyaslavl line, instanceOf, medieval princely line]
-
A.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
B.
ducal line
A ducal line is a hereditary lineage descending from or associated with a duke, typically holding noble titles, privileges, and succession rights within a feudal or monarchical system.
-
C.
Rurikid princely branch
chosen
A Rurikid princely branch is a dynastic line descending from the medieval Rurikid ruling family, typically associated with governance over a specific principality or territory in Kievan Rus’ and its successor states.
-
D.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
E.
medieval French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:44 a.m.