Triple
T7682123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince Rudolf of Austria |
E174020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-Hungarian crown prince |
C6184
|
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: Austro-Hungarian crown prince Context triple: [Crown Prince Rudolf of Austria, instanceOf, Austro-Hungarian crown prince]
-
A.
Archduke of Austria
chosen
The Archduke of Austria was a noble title used primarily by members of the Habsburg dynasty, denoting high-ranking princes of the Austrian territories within the Holy Roman Empire and later the Austro-Hungarian Empire.
-
B.
Duke of Reichstadt
The Duke of Reichstadt is a noble title historically associated with Napoleon II, the son of Napoleon Bonaparte, symbolizing his status and claims within European aristocracy.
-
C.
Duke of Austria
The Duke of Austria was a high-ranking noble title in the Holy Roman Empire, held by rulers of the Austrian lands who governed the region and often played a significant role in European politics.
-
D.
Emperor of Austria
The Emperor of Austria was the hereditary sovereign of the Austrian Empire (and later the Austro-Hungarian Empire), holding supreme political and symbolic authority over its diverse territories and peoples from 1804 to 1918.
-
E.
Duke of Bavaria
The Duke of Bavaria is a noble title historically held by the ruler of the Bavarian duchy, signifying high-ranking authority and governance within the region of Bavaria in the Holy Roman Empire and later German territories.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:01 p.m.