Triple
T10646649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Austria |
E250851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg hereditary land |
C24596
|
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: Habsburg hereditary land Context triple: [Inner Austria, instanceOf, Habsburg hereditary land]
-
A.
core territory of the Habsburg monarchy
chosen
The core territory of the Habsburg monarchy refers to the central, hereditary lands—primarily Austria and later including Bohemia and Hungary—that formed the political, administrative, and dynastic heart of Habsburg rule in Europe.
-
B.
hereditary principality
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
C.
Ernestine duchy
The Ernestine duchy refers to any of the small, historically fragmented German principalities in Thuringia ruled by the Ernestine branch of the Wettin dynasty after the partition of Saxony.
-
D.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
-
E.
institution of the Kingdom of Hungary
An institution of the Kingdom of Hungary is an organized body or establishment—political, legal, religious, educational, or administrative—that operated within and under the authority of the historical Kingdom of Hungary.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:05 p.m.