Triple
T20092580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Данило Романович |
E496309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | представник династії Романовичів |
C42841
|
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: представник династії Романовичів Context triple: [Данило Романович, instanceOf, представник династії Романовичів]
-
A.
Gediminid dynasty member
A Gediminid dynasty member is an individual descended from or belonging to the medieval ruling house founded by Grand Duke Gediminas, which governed the Grand Duchy of Lithuania and its successor states.
-
B.
Jagiellonian dynasty member
A Jagiellonian dynasty member is an individual belonging to the royal house that ruled parts of Central and Eastern Europe, including Poland, Lithuania, Bohemia, and Hungary, from the late 14th to the 16th century.
-
C.
Polish dynasty
A Polish dynasty is a hereditary ruling family originating from Poland that holds political power and influence over the country or its territories across successive generations.
-
D.
Piast dynasty member
A Piast dynasty member is an individual belonging to the first historical ruling dynasty of Poland, which governed various Polish and regional territories from the 10th to the 14th century (and in some branches beyond).
-
E.
member of the Dolgorukov family
A member of the Dolgorukov family is an individual belonging to the historically prominent Russian noble house of Dolgorukov, known for its political influence, military service, and close ties to the ruling dynasties.
- F. None of above. chosen
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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:22 p.m.