Triple
T11832508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Karl von Lichnowsky |
E281427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austrian aristocrat |
C7273
|
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: Austrian aristocrat Context triple: [Prince Karl von Lichnowsky, instanceOf, Austrian aristocrat]
-
A.
Austrian noble
chosen
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
B.
Belgian aristocrat
A Belgian aristocrat is a member of Belgium’s hereditary nobility, typically bearing a noble title, upholding longstanding family traditions, and often participating in the country’s cultural, social, and sometimes political life.
-
C.
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.
-
D.
Austrian archduchess
An Austrian archduchess is a female member of the Habsburg or Habsburg-Lorraine dynasty, traditionally bearing the noble title associated with the Archduchy of Austria and often involved in dynastic politics, court life, and diplomatic marriages.
-
E.
Austrian person of Polish descent
An Austrian person of Polish descent is an individual who holds or identifies with Austrian nationality or culture while having familial, ancestral, or ethnic roots in Poland.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.