Triple
T33866576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine of Hungary (1370–1378) |
E868072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval princess |
C2525
|
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: medieval princess Context triple: [Catherine of Hungary (1370–1378), instanceOf, medieval princess]
-
A.
princess
chosen
A princess is a royal female, typically the daughter or close relative of a monarch, who often embodies nobility, grace, and ceremonial or symbolic leadership within a kingdom or realm.
-
B.
Saxon princess
A Saxon princess is a noblewoman of royal Saxon lineage, typically characterized by her political significance in dynastic alliances, cultural influence within early medieval Germanic society, and role in consolidating power through marriage and patronage.
-
C.
medieval English noblewoman
A medieval English noblewoman is an aristocratic woman of high social rank in England’s Middle Ages, whose life centers on managing estates, forging political alliances through marriage, and upholding the social, cultural, and religious expectations of the nobility.
-
D.
English princess
An English princess is a female member of the British royal family, typically the daughter or close female relative of a monarch or prince, who holds the title of "Princess" and often undertakes ceremonial, charitable, and representational duties.
-
E.
medieval royal
A medieval royal is a sovereign or high-ranking noble who holds hereditary power and authority over a kingdom or territory within the sociopolitical and cultural structures of the Middle Ages.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.