Triple
T35693272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilian Thomas of Austria |
E1031362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century Austrian noble |
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: 17th-century Austrian noble Context triple: [Maximilian Thomas of Austria, instanceOf, 17th-century Austrian noble]
-
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.
Bohemian nobleman
A Bohemian nobleman is an aristocrat from the historical Kingdom of Bohemia, distinguished by hereditary titles, landownership, and a role in the region’s political and cultural life.
-
C.
Austrian countess
An Austrian countess is a noblewoman holding the hereditary or honorary title of countess within the historical or contemporary aristocracy of Austria.
-
D.
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.
-
E.
18th-century German prince
An 18th-century German prince is a male hereditary ruler or high-ranking noble of one of the many semi-autonomous German states within the Holy Roman Empire, wielding regional political, military, and cultural influence under a complex feudal and imperial framework.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.