Triple
T2895970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert I of Monaco |
E63940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Monaco |
C11650
|
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 Monaco Context triple: [Albert I of Monaco, instanceOf, Prince of Monaco]
-
A.
Princess of Monaco
A Princess of Monaco is a female member of the Monegasque princely family, typically by birth or marriage, who holds a royal title and may perform ceremonial, charitable, and representational duties for the Principality of Monaco.
-
B.
Duke of Savoy
The Duke of Savoy was the hereditary ruler of the historical Duchy of Savoy, a significant European principality that played a key role in the politics of Italy and France from the late Middle Ages until its elevation to a kingdom.
-
C.
King of Sardinia
The King of Sardinia was the hereditary monarch who ruled the Kingdom of Sardinia, a European state centered on the island of Sardinia and later including Piedmont and other mainland territories, until its absorption into the unified Kingdom of Italy in the 19th century.
-
D.
Grand Duke of Tuscany
The Grand Duke of Tuscany was the sovereign ruler of the Grand Duchy of Tuscany, a central Italian state, holding hereditary monarchical authority over its political, military, and economic affairs.
-
E.
Duke of Orléans
The Duke of Orléans is a French noble title traditionally held by a close male relative of the reigning king, often associated with significant political influence, territorial holdings around Orléans, and a prominent role in royal succession and court affairs.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:08 p.m.