Triple
T19012258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herleve |
E465256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval woman |
C3415
|
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 woman Context triple: [Herleve, instanceOf, medieval woman]
-
A.
12th-century noblewoman
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.
-
B.
medieval people
chosen
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
C.
medieval Bulgarian noblewoman
A medieval Bulgarian noblewoman is an aristocratic female member of Bulgarian society during the Middle Ages, typically associated with landownership, political influence, and participation in courtly and religious life.
-
D.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
-
E.
13th-century German woman
A 13th-century German woman is a female inhabitant of the German-speaking regions of medieval Europe whose life was shaped by feudal structures, Christian religiosity, and gendered social roles in family, work, and community.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.