Triple
T34314275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theresa of Portugal, Countess of Flanders |
E880534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | countess consort of Flanders |
C35546
|
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 consort of Flanders Context triple: [Theresa of Portugal, Countess of Flanders, instanceOf, countess consort of Flanders]
-
A.
Countess of Hainaut
The Countess of Hainaut is a noblewoman who holds, by birth or marriage, the comital title associated with the medieval County of Hainaut, historically located in what is now parts of Belgium and northern France.
-
B.
Countess consort of Guelders
A Countess consort of Guelders is the wife of the reigning Count of Guelders, holding the title and associated social status through marriage rather than by hereditary right.
-
C.
Duchess consort of Brabant
The Duchess consort of Brabant is the wife of the reigning Duke of Brabant, holding a ceremonial and social role within the duchy's nobility without exercising sovereign authority in her own right.
-
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
chosen
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.
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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.