Triple
T8412087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Félix of Luxembourg |
E198648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Luxembourg |
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: Prince of Luxembourg Context triple: [Prince Félix of Luxembourg, instanceOf, Prince of Luxembourg]
-
A.
Luxembourgian prince
chosen
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.
-
B.
Duke of Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:05 p.m.