Triple
T1099672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis-Auguste de Bourbon, Duke of Maine |
E24349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Maine |
C7033
|
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: Duke of Maine Context triple: [Louis-Auguste de Bourbon, Duke of Maine, instanceOf, Duke of Maine]
-
A.
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.
-
B.
Duke of Normandy
The Duke of Normandy was a medieval noble title denoting the sovereign or semi-sovereign ruler of the Duchy of Normandy, a powerful feudal territory in northwestern France that played a pivotal role in European politics, especially after its dukes became kings of England.
-
C.
Prince of Orange
The Prince of Orange is a hereditary noble title historically associated with the sovereign rulers of the Principality of Orange and later with the heir apparent to the Dutch throne.
-
D.
King of Hanover
The King of Hanover was the hereditary monarch and head of state of the Kingdom of Hanover, a German kingdom that existed from 1814 to 1866, ruling over its government, military, and foreign affairs.
-
E.
English prince
An English prince is a male member of the British royal family, typically a son or close male-line descendant of the monarch, who holds the title of "Prince" and may perform ceremonial, diplomatic, and public duties on behalf of the Crown.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.