Triple
T2611913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Elisabeth Lämmerhirt |
E58793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century German woman |
C5873
|
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: 17th-century German woman Context triple: [Maria Elisabeth Lämmerhirt, instanceOf, 17th-century German woman]
-
A.
17th-century German person
chosen
A 17th-century German person is an individual who lived in the German-speaking regions of Central Europe between 1601 and 1700, shaped by the political fragmentation of the Holy Roman Empire, the Thirty Years’ War, and the cultural currents of the Baroque era.
-
B.
Swedish noblewoman
A Swedish noblewoman is a woman belonging to the hereditary or conferred nobility of Sweden, typically associated with specific titles, estates, and social privileges within Swedish aristocratic society.
-
C.
18th-century English woman
An 18th-century English woman is a female individual living in England between 1701 and 1800, whose daily life, rights, social roles, and opportunities are shaped by class, gender norms, and the political and cultural changes of the Georgian era.
-
D.
Bavarian princess
A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
-
E.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.