Triple
T19320955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margaret II of Flanders |
E483221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Hainaut |
C41921
|
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 Hainaut Context triple: [Margaret II of Flanders, instanceOf, Countess of Hainaut]
-
A.
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.
-
B.
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.
-
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 Champagne
The Countess of Champagne is a noblewoman who holds the hereditary or marital title associated with ruling or representing the County of Champagne within the medieval French aristocracy.
-
E.
Duchess of Burgundy
The Duchess of Burgundy is a high-ranking noblewoman who holds the ducal title of Burgundy, often wielding significant political influence, overseeing courtly affairs, and managing the territories and alliances associated with the Burgundian domain.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:32 p.m.