Triple
T31222767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Robert of Luxembourg |
E796059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Luxembourgish noble |
C58584
|
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: Luxembourgish noble Context triple: [Prince Robert of Luxembourg, instanceOf, Luxembourgish noble]
-
A.
Luxembourgish noble
chosen
A Luxembourgish noble is a member of the hereditary aristocracy of Luxembourg, historically holding titles, land, and social privileges within the Grand Duchy’s feudal and later constitutional systems.
-
B.
Luxembourgian royal
A Luxembourgian royal is a member of the Grand Ducal Family of Luxembourg, holding hereditary titles and performing constitutional, ceremonial, and representative duties for the Grand Duchy.
-
C.
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.
-
D.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
-
E.
Savoyard noble
A Savoyard noble is a member of the aristocracy from the historical region and Duchy of Savoy, holding hereditary titles, land, and political influence within its feudal and later dynastic structures.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.