Triple
T18071518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aulic War Council in Vienna |
E432440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg institution |
C35975
|
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 institution Context triple: [Aulic War Council in Vienna, instanceOf, Habsburg institution]
-
A.
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.
-
B.
institution of Austria-Hungary
chosen
An institution of Austria-Hungary is an organized body or establishment—political, legal, military, educational, or cultural—created or officially recognized within the dual monarchy of Austria-Hungary (1867–1918) to perform specific governmental or societal functions.
-
C.
Habsburg monarch
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
D.
Count of Habsburg
A Count of Habsburg is a noble title historically held by members of the Habsburg dynasty, denoting a regional ruler or high-ranking aristocrat within the Holy Roman Empire and later Habsburg realms.
-
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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.