Triple
T11806890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roswitha Eberl |
E280768
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object |
Roswitha
Roswitha is a feminine given name of Germanic origin, historically associated with medieval writers and commonly used in German-speaking countries.
|
E947293
|
NE FINISHED |
How this triple was built (4 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Roswitha | Statement: [Roswitha Eberl, givenName, Roswitha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roswitha Context triple: [Roswitha Eberl, givenName, Roswitha]
-
A.
Hiltrud
Hiltrud was a Frankish noblewoman of the early Middle Ages, known primarily as a member of the royal family connected to Charlemagne’s circle.
-
B.
Goswintha
Goswintha was a Visigothic queen consort, known as the influential and often controversial wife of King Leovigild in 6th-century Hispania.
-
C.
Ermentrud
Ermentrud is a given name, typically a historical or medieval European female name, that serves as a variant form of Ermintrude.
-
D.
Himiltrude
Himiltrude was a Frankish noblewoman, traditionally regarded as Charlemagne’s first partner and the mother of his son Pepin the Hunchback.
-
E.
Luitgard
Luitgard was the fourth and last wife of Charlemagne, serving briefly as Frankish queen consort in the late 8th century.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Roswitha Triple: [Roswitha Eberl, givenName, Roswitha]
Generated description
Roswitha is a feminine given name of Germanic origin, historically associated with medieval writers and commonly used in German-speaking countries.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Roswitha Target entity description: Roswitha is a feminine given name of Germanic origin, historically associated with medieval writers and commonly used in German-speaking countries.
-
A.
Hiltrud
Hiltrud was a Frankish noblewoman of the early Middle Ages, known primarily as a member of the royal family connected to Charlemagne’s circle.
-
B.
Goswintha
Goswintha was a Visigothic queen consort, known as the influential and often controversial wife of King Leovigild in 6th-century Hispania.
-
C.
Ermentrud
Ermentrud is a given name, typically a historical or medieval European female name, that serves as a variant form of Ermintrude.
-
D.
Himiltrude
Himiltrude was a Frankish noblewoman, traditionally regarded as Charlemagne’s first partner and the mother of his son Pepin the Hunchback.
-
E.
Luitgard
Luitgard was the fourth and last wife of Charlemagne, serving briefly as Frankish queen consort in the late 8th century.
- F. None of above. chosen
Provenance (5 batches)
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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5c8324481909a54852a9bb714e0 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f131726ab08190ae777bee3ac6df43 |
completed | April 28, 2026, 10:15 p.m. |
| NEDg | Description generation | batch_69f141b1c50c819081a8055d951a49de |
completed | April 28, 2026, 11:24 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f14fcb63208190ad1185ad66314fa9 |
completed | April 29, 2026, 12:24 a.m. |
Created at: April 8, 2026, 9:42 p.m.