Triple
T23162380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Höfle |
E578619
|
entity |
| Predicate | subjectOf |
P38
|
FINISHED |
| Object | Höfle Telegram |
—
|
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: Höfle Telegram | Statement: [Hermann Höfle, subjectOf, Höfle Telegram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Höfle Telegram Context triple: [Hermann Höfle, subjectOf, Höfle Telegram]
-
A.
Höfle Telegram
chosen
The Höfle Telegram was a secret 1943 Nazi radio message that detailed the number of Jews murdered in Operation Reinhard extermination camps, later becoming key evidence of the scale of the Holocaust.
-
B.
Hauerland
Hauerland was a historical German-speaking enclave in central Slovakia, settled by Carpathian Germans in the Middle Ages.
-
C.
Hechtel
Hechtel is a village in the Belgian municipality of Hechtel-Eksel, located in the province of Limburg.
-
D.
Höfle
Höfle is a German-language surname most notably associated with SS officer Hermann Höfle, a key organizer of the Holocaust’s Operation Reinhard.
-
E.
Höfle
Höfle is a small settlement that forms part of the municipality of Umhausen in the Tyrol region of Austria.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f019cd881908e3c68d99454da2a |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:02 p.m.