Triple
T24437702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallsee family |
E616169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Austrian noble lineage |
C22820
|
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 Austrian noble lineage Context triple: [Wallsee family, instanceOf, medieval Austrian noble lineage]
-
A.
Austrian noble
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.
Austrian nobility
chosen
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.
-
C.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
-
D.
Hungarian noble family
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.
-
E.
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.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:16 a.m.