Triple
T5076743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humbert I, Count of Savoy |
E114415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Count of Savoy |
C17498
|
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 Savoy Context triple: [Humbert I, Count of Savoy, instanceOf, Count of Savoy]
-
A.
Count of Provence
The Count of Provence is a noble title historically held by the ruler of the County of Provence, a medieval feudal territory in what is now southeastern France, signifying both regional governance and aristocratic status.
-
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.
Duke of Piacenza
The Duke of Piacenza is a noble title historically associated with the governance and aristocratic leadership of the Piacenza region in northern Italy.
-
D.
Duke of Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
-
E.
Duke of Parma
The Duke of Parma is a noble title historically associated with the ruler of the Duchy of Parma in northern Italy, often held by members of prominent European royal families.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:39 p.m.