Triple
T17812173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clementia of Habsburg |
E444737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Tyrol |
C39177
|
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: Countess of Tyrol Context triple: [Clementia of Habsburg, instanceOf, Countess of Tyrol]
-
A.
Duchess of Savoy
The Duchess of Savoy is a noblewoman who holds the ducal consort or sovereign title associated with the historical Duchy of Savoy, often playing significant political, dynastic, and ceremonial roles within European aristocracy.
-
B.
Countess of Sicily
The Countess of Sicily is a noblewoman holding the comital title associated with the island of Sicily, historically signifying high aristocratic rank, territorial authority, and dynastic influence within the Sicilian realm.
-
C.
Countess of Burgundy
The Countess of Burgundy is a noblewoman who holds or is married to the holder of the feudal title governing the historic County of Burgundy, wielding significant regional authority, land rights, and dynastic influence.
-
D.
Countess of Holland
The Countess of Holland is a noble title historically held by the wife or female ruler associated with the medieval County of Holland in the Low Countries, signifying high aristocratic status and territorial influence.
-
E.
Countess of Flanders
The Countess of Flanders is a noblewoman who holds, by inheritance or marriage, the comital title associated with the medieval County of Flanders, often wielding significant political, economic, and dynastic influence in the region.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:14 a.m.