Triple
T37638502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renewed Ordinance of the Land (1627) |
E936551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg-imposed constitution |
C62949
|
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-imposed constitution Context triple: [Renewed Ordinance of the Land (1627), instanceOf, Habsburg-imposed constitution]
-
A.
style of the Habsburg monarchy
The style of the Habsburg monarchy is a grand, eclectic blend of Baroque opulence, Catholic symbolism, and imperial pageantry that projects dynastic power, continuity, and hierarchical order across architecture, ceremony, and visual culture.
-
B.
interwar constitution
An interwar constitution is a national fundamental law enacted between World War I and World War II that reflects the era’s political upheavals, ideological conflicts, and experiments with new forms of democracy and authoritarianism.
-
C.
Stand des Heiligen Römischen Reiches
Ein Stand des Heiligen Römischen Reiches war eine rechtlich anerkannte Körperschaft oder Person (z.B. Fürst, Reichsstadt, geistlicher Herr), die im Reichsverband eigene Hoheitsrechte besaß und in den Reichsständen vertreten war.
-
D.
Reichsreform
Reichsreform bezeichnet die im Spätmittelalter und in der Frühen Neuzeit unternommenen Versuche, die Verfassung, Verwaltung und Gerichtsbarkeit des Heiligen Römischen Reiches grundlegend zu ordnen und zu modernisieren.
-
E.
Habsburg possession
A Habsburg possession is any territory, domain, or holding under the political authority or dynastic control of the Habsburg family at a given time.
- F. None of above. chosen
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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.