Triple
T29103808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ereleuva |
E736708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic noblewoman |
C19263
|
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: Gothic noblewoman Context triple: [Ereleuva, instanceOf, Gothic noblewoman]
-
A.
Gothic heroine
A Gothic heroine is a typically young, vulnerable yet resilient woman who navigates mysterious, threatening, and often supernatural environments, confronting psychological terror, oppressive forces, and dark secrets to seek truth and autonomy.
-
B.
Renaissance noblewoman
A Renaissance noblewoman is an elite woman of the 14th–17th centuries whose life is shaped by courtly culture, dynastic politics, patronage of the arts, and strict social and gender hierarchies.
-
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.
13th-century noblewoman
A 13th-century noblewoman is an aristocratic woman of medieval Europe who holds social status and influence through lineage, marriage, and land-based power within a feudal hierarchy.
-
E.
12th-century noblewoman
chosen
A 12th-century noblewoman is an aristocratic woman of medieval Europe who wields social, economic, and sometimes political influence through landholding, marriage alliances, and the management of her household and estates within a feudal hierarchy.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:14 a.m.