Triple
T13763255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques, Hereditary Prince of Monaco |
E330668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Monegasque prince |
C32614
|
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: Monegasque prince Context triple: [Jacques, Hereditary Prince of Monaco, instanceOf, Monegasque prince]
-
A.
Monégasque prince
chosen
A Monégasque prince is a male member of the ruling Grimaldi family or the princely house of Monaco, holding a dynastic title within the sovereign principality of Monaco.
-
B.
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.
-
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.
Marquis of Provence
The Marquis of Provence is a noble title historically granted to the feudal ruler of the borderland region of Provence, responsible for its military defense, administration, and representation within the broader realm.
-
E.
prince of Savoy
A prince of Savoy is a male member of the historic House of Savoy, often holding hereditary titles and political or military influence within the Savoyard states and later the Kingdom of Italy.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:10 p.m.