Triple
T14948133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques de Wissant |
E372719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | burgher of Calais |
C35305
|
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: burgher of Calais Context triple: [Jacques de Wissant, instanceOf, burgher of Calais]
-
A.
Duke of Brittany
The Duke of Brittany was the sovereign or semi-sovereign ruler of the historical Duchy of Brittany in western France, holding feudal authority, managing regional governance, and often navigating complex political relations with the French crown and neighboring powers.
-
B.
Duke of Narbonne
The Duke of Narbonne is a high-ranking noble title historically associated with the governance, military leadership, and social prestige of the Narbonne region within a larger feudal realm.
-
C.
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.
-
D.
Duke of Burgundy
The Duke of Burgundy is a high-ranking noble title historically associated with the powerful rulers of the Burgundy region, often serving as influential political and military leaders in medieval and early modern Europe.
-
E.
Count of Anjou
The Count of Anjou was a medieval noble title in western France whose holders controlled the strategically important county of Anjou and often played a pivotal role in French and English royal politics.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:39 a.m.