Triple
T707142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schutzstaffel |
E14124
|
entity |
| Predicate | symbol |
P129
|
FINISHED |
| Object | SS runes |
E84159
|
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: SS runes | Statement: [Schutzstaffel, symbol, SS runes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SS runes Context triple: [Schutzstaffel, symbol, 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.
Runic alphabet
The Runic alphabet is an ancient writing system used by Germanic peoples, primarily for inscriptions in early Germanic languages across Northern Europe and Scandinavia.
-
C.
Runasimi
Runasimi is the Indigenous Quechuan language family of the Andes, historically associated with the Inca Empire and still widely spoken across several South American countries.
-
D.
Midgard
Midgard is the human-inhabited world in Norse mythology, situated between the realms of gods and giants and encircled by a vast ocean.
-
E.
RAN
RAN is the 3GPP working group responsible for specifying the radio access network technologies used in mobile communication systems such as LTE and 5G.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5477bb48190a2032edc83a24720 |
completed | March 1, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a63755d1f081909f214ab8d497f096 |
completed | March 3, 2026, 1:20 a.m. |
Created at: March 1, 2026, 7:36 p.m.