Triple
T19010714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS officer |
E465215
|
entity |
| Predicate | usedInsignia |
P1617
|
FINISHED |
| Object | SS runes |
—
|
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: SS runes | Statement: [SS officer, usedInsignia, SS runes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SS runes Context triple: [SS officer, usedInsignia, SS runes]
-
A.
SS runes
chosen
SS runes are a stylized double-sig rune insignia used by the Schutzstaffel (SS), symbolizing Nazi ideology and now widely recognized as a hate symbol.
-
B.
SS Runic
SS Runic was a British cargo steamship built in the early 20th century that later became known as SS Imo, the vessel involved in the 1917 Halifax Explosion.
-
C.
Rune
Rune is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
D.
Rúnatal
Rúnatal is a section of the Old Norse poem Hávamál in which Odin recounts his self-sacrifice and the discovery of runes, central to Norse mythological and magical tradition.
-
E.
Runemo
Runemo is a small locality situated within Ovanåker Municipality in Gävleborg County, Sweden.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a8225c81908e80ae7eb1c1301b |
completed | April 20, 2026, 7:32 a.m. |
Created at: April 10, 2026, 12:02 p.m.