Triple
T7239327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume, Hereditary Grand Duke of Luxembourg |
E155314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Luxembourgian prince |
C20968
|
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: Luxembourgian prince Context triple: [Guillaume, Hereditary Grand Duke of Luxembourg, instanceOf, Luxembourgian prince]
-
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.
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.
-
C.
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.
-
D.
Christian prince
A Christian prince is a sovereign or ruling noble whose authority and governance are explicitly shaped by Christian beliefs, values, and ecclesiastical relationships.
-
E.
Belgian princess
A Belgian princess is a female member of the Belgian royal family, typically the daughter or close female relative of the reigning monarch or heir to the throne, who may undertake ceremonial, diplomatic, and charitable duties on behalf of the kingdom.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:55 p.m.