Triple
T1336444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippe II, Duke of Orléans |
E28760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Orléans |
C6254
|
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 Orléans Context triple: [Philippe II, Duke of Orléans, instanceOf, Duke of Orléans]
-
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.
King of France
The King of France is the sovereign monarch who historically ruled the Kingdom of France, embodying supreme political authority, symbolic national leadership, and dynastic continuity until the abolition of the monarchy.
-
C.
Louis XIV war
A Louis XIV war is a large-scale, dynastic conflict driven by the French king’s pursuit of territorial expansion, political dominance, and prestige in 17th–18th century Europe, typically involving shifting coalitions of major powers.
-
D.
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.
-
E.
King of Holland
The King of Holland is the hereditary head of state of the Netherlands, representing national unity, performing constitutional and ceremonial duties, and serving as a symbolic figure domestically and internationally.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.