Triple
T1124561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis de Bourbon, Count of Vermandois |
E24689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Count of Vermandois |
C7580
|
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: Count of Vermandois Context triple: [Louis de Bourbon, Count of Vermandois, instanceOf, Count of Vermandois]
-
A.
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.
-
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 Westphalia
The King of Westphalia was the sovereign ruler of the short-lived Kingdom of Westphalia (1807–1813), a Napoleonic client state in central Europe governed primarily by Napoleon’s brother Jérôme Bonaparte.
-
D.
Prince of Antioch
A Prince of Antioch is a sovereign or noble ruler of the medieval Crusader state centered on the city of Antioch, holding political, military, and often feudal authority over the principality and its territories.
-
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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:44 p.m.