Triple
T14717652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franziska Kronberger |
E345724
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Franziska |
E83113
|
NE FINISHED |
How this triple was built (2 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: Franziska | Statement: [Franziska Kronberger, givenName, Franziska]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Franziska Context triple: [Franziska Kronberger, givenName, Franziska]
-
A.
Franziska
chosen
Franziska is a feminine given name of German origin, closely related to and cognate with the name Frances.
-
B.
Fricka
Fricka is the goddess of marriage and the jealous, morally rigid wife of Wotan in Richard Wagner’s Ring Cycle.
-
C.
Verena
Verena is a feminine given name of Latin origin, commonly used in German-speaking and other European countries.
-
D.
Gisela
Gisela was a daughter of the West Frankish king and Holy Roman Emperor Charles the Bald, belonging to the Carolingian royal dynasty of the 9th century.
-
E.
Gisela
Gisela was a daughter of Charlemagne, the Frankish king and first Holy Roman Emperor, and a member of the Carolingian royal family.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf0935f088190b54f2e106532972a |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:29 a.m.