Triple
T30938587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadeusz Kossak |
E788195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Kossak family |
C60058
|
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: member of Kossak family Context triple: [Tadeusz Kossak, instanceOf, member of Kossak family]
-
A.
member of Kolisch family
A member of the Kolisch family is an individual belonging by birth or legal relation to the historically notable Kolisch lineage, recognized for its cultural, intellectual, or social contributions.
-
B.
member of the Sobieski family
A member of the Sobieski family is an individual belonging by birth or legal relation to the historically significant Polish noble and royal lineage associated with the Sobieski name.
-
C.
member of Benois family
A member of the Benois family is an individual belonging to the historically significant Benois lineage, known for its influential contributions to the arts, architecture, and culture.
-
D.
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.
-
E.
member of the Godunov family
A member of the Godunov family is an individual belonging to a historically significant Russian noble lineage, often associated with political influence, landownership, and cultural heritage in Russia.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:52 p.m.