Triple
T19539912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Nelson |
E488869
|
entity |
| Predicate | enemy |
P4567
|
FINISHED |
| Object | Wotan |
—
|
NE NERFINISHED |
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: Wotan | Statement: [Kent Nelson, enemy, Wotan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wotan Context triple: [Kent Nelson, enemy, Wotan]
-
A.
Wotan
chosen
Wotan is a powerful and ancient sorcerer supervillain in DC Comics, known primarily as one of Doctor Fate’s most formidable mystical adversaries.
-
B.
Alberich
Alberich is a figure from Germanic and Norse legend, often depicted as a powerful dwarf or elf associated with treasure and magical knowledge.
-
C.
Brünnhilde
Brünnhilde is a legendary Valkyrie heroine from Germanic and Norse mythology, most famously depicted in Richard Wagner’s "Ring" cycle as a warrior maiden who defies the gods for love.
-
D.
Wotan II
Wotan II was the Allied codename for the German World War II radio navigation system Y-Gerät, used by the Luftwaffe for precision bombing.
-
E.
Sigfred
Sigfred was a Viking leader known for commanding Norse forces during the late 9th-century siege of Paris.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63871d00881909ed7371ae5577957 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 10, 2026, 1:41 p.m.