Triple
T13450875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Báthory family |
E320603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian noble dynasty |
C27403
|
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: Hungarian noble dynasty Context triple: [Báthory family, instanceOf, Hungarian noble dynasty]
-
A.
Hungarian noble family
chosen
A Hungarian noble family is a historically recognized lineage within the Kingdom of Hungary’s aristocracy, holding hereditary titles, lands, and social privileges passed down through generations.
-
B.
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.
-
C.
Habsburg
Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
-
D.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
E.
Austrian nobility
Austrian nobility refers to the historically privileged hereditary elite of the Habsburg-ruled territories, characterized by titles, landownership, and a distinct social and political status within the Austrian Empire and its predecessor states.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:41 p.m.