Triple
T27300308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margaret of Hungary |
E688886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin Empress consort |
C51707
|
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: Latin Empress consort Context triple: [Margaret of Hungary, instanceOf, Latin Empress consort]
-
A.
Latin Empress consort of Constantinople
chosen
A Latin Empress consort of Constantinople was the wife of a Latin Emperor who ruled the Byzantine capital after the Fourth Crusade, holding a ceremonial and dynastic role within the Latin Empire’s court.
-
B.
Holy Roman Empress consort
A Holy Roman Empress consort is the wife of a reigning Holy Roman Emperor, holding the empire’s highest female title and often exercising ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
-
C.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
D.
Despotess consort
A despotess consort is the spouse or partner of an absolute female ruler, wielding influence and status derived from her intimate association with the despotess’s autocratic power.
-
E.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:21 a.m.