Triple
T21150623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis of Savoy (bishop) |
E521177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Savoyard prince |
C25051
|
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: Savoyard prince Context triple: [Louis of Savoy (bishop), instanceOf, Savoyard prince]
-
A.
prince of Savoy
chosen
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.
-
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.
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.
-
D.
Monégasque prince
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.
-
E.
prince of Bourbon-Parma
A prince of Bourbon-Parma is a male member of the Bourbon-Parma branch of the House of Bourbon, historically holding dynastic titles and connections to various European royal families.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.