Triple
T5116254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicherheitsdienst |
E115341
|
entity |
| Predicate | division |
P889
|
FINISHED |
| Object | Ausland-SD |
E85107
|
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: Ausland-SD | Statement: [Sicherheitsdienst, division, Ausland-SD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ausland-SD Context triple: [Sicherheitsdienst, division, Ausland-SD]
-
A.
Ausland-SD
chosen
Ausland-SD was the foreign intelligence branch of Nazi Germany’s SS Security Service responsible for espionage and information gathering outside the Reich.
-
B.
Inland-SD
Inland-SD is a regional division of the SS Security Service (SD), responsible for domestic intelligence and security operations within Nazi Germany.
-
C.
SDUSA
SDUSA is an American social-democratic political organization that emerged from the Socialist Party of America and advocates for democratic socialism and progressive reforms.
-
D.
USAIS
USAIS is the U.S. Army’s primary institution for training, educating, and developing infantry soldiers and leaders.
-
E.
US-SD
US-SD is the ISO 3166-2 subdivision code that uniquely identifies the U.S. state of South Dakota.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cfa9f88190aa7dfd264e554899 |
completed | March 20, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bebaadfaac8190aa0407196e5c4c20 |
completed | March 21, 2026, 3:35 p.m. |
Created at: March 20, 2026, 1:41 p.m.