Triple
T14662178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundians |
E344271
|
entity |
| Predicate | king |
P403
|
FINISHED |
| Object | Gundahar (Gunther) |
E468302
|
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: Gundahar (Gunther) | Statement: [Burgundians, king, Gundahar (Gunther)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gundahar (Gunther) Context triple: [Burgundians, king, Gundahar (Gunther)]
-
A.
Gundahar (Gunther)
chosen
Gundahar, also known as Gunther, was a legendary early king of the Burgundians who figures prominently in Germanic heroic tradition, including the Nibelungen saga.
-
B.
Eckhard
Eckhard is a masculine given name of German origin, commonly used in German-speaking countries.
-
C.
Ingenried
Ingenried is a small rural municipality in the Weilheim-Schongau district of Bavaria in southern Germany.
-
D.
Gundemar
Gundemar was a 7th-century Visigothic king of Hispania and Septimania who ruled briefly before being succeeded by Sisebut.
-
E.
Gereon
Gereon is a masculine given name of German origin, historically borne by several saints and nobles.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51c84448190a1f5fa9ab8a1e2c4 |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5e4789481909a64622a1d284373 |
completed | May 8, 2026, 12:24 p.m. |
Created at: April 10, 2026, 1:27 a.m.