Triple
T4539049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans-Adam II |
E107481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Liechtenstein |
C17137
|
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: Prince of Liechtenstein Context triple: [Hans-Adam II, instanceOf, Prince of Liechtenstein]
-
A.
Prince of Monaco
The Prince of Monaco is the hereditary sovereign ruler and head of state of the Principality of Monaco, responsible for its governance, representation, and continuity of the Grimaldi dynasty.
-
B.
Grand Duke of Hesse
The Grand Duke of Hesse was the hereditary sovereign ruler of the Grand Duchy of Hesse, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
-
C.
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.
-
D.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
E.
Archduke of Austria
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.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.