Triple
T24584381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Marie-Caroline of Liechtenstein |
E608342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Liechtenstein princess |
C45473
|
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 princess Context triple: [Princess Marie-Caroline of Liechtenstein, instanceOf, Liechtenstein princess]
-
A.
princess of Neuchâtel
A princess of Neuchâtel is a noblewoman holding or bearing the hereditary or consort title associated with the historic principality of Neuchâtel in what is now western Switzerland.
-
B.
Liechtenstein royal
chosen
A Liechtenstein royal is a member of the princely family of Liechtenstein, holding hereditary titles and roles connected to the governance, representation, and traditions of the Principality of Liechtenstein.
-
C.
Grand Duchess of Luxembourg
The Grand Duchess of Luxembourg is the title held by the female sovereign or consort of the Grand Duke, serving as a central figure in the grand ducal family and the ceremonial life of the Grand Duchy of Luxembourg.
-
D.
Prince of Liechtenstein
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.
-
E.
Princess consort of Liechtenstein
The Princess consort of Liechtenstein is the wife of the reigning Prince of Liechtenstein, who supports the monarch in ceremonial, social, and charitable duties but does not hold sovereign authority.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.