Triple
T21727830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Leopold Emanuel of Liechtenstein |
E536318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Liechtenstein prince |
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: Liechtenstein prince Context triple: [Prince Leopold Emanuel of Liechtenstein, instanceOf, Liechtenstein prince]
-
A.
Prince of Liechtenstein
chosen
The Prince of Liechtenstein is the hereditary head of state of the Principality of Liechtenstein, holding significant political authority alongside symbolic and representative duties within the constitutional monarchy.
-
B.
Luxembourgian prince
A Luxembourgian prince is a male member of the Grand Ducal Family of Luxembourg who holds the princely title by birth or marriage within the country's constitutional monarchy.
-
C.
Monégasque prince
A Monégasque prince is a male member of the ruling Grimaldi family or the princely house of Monaco, holding a dynastic title within the sovereign principality of Monaco.
-
D.
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.
-
E.
Duke of Luxembourg
The Duke of Luxembourg is a noble title historically associated with the ruler or high-ranking aristocrat of the Luxembourg region, often linked to European dynastic and political affairs.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:48 p.m.