Triple
T23162350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Höfle |
E578619
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Höfle |
—
|
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 | Statement: [Hermann Höfle, familyName, Höfle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Höfle Context triple: [Hermann Höfle, familyName, Höfle]
-
A.
Höfle
chosen
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.
-
B.
Höfle
Höfle is a small settlement that forms part of the municipality of Umhausen in the Tyrol region of Austria.
-
C.
Waltershof
Waltershof is an industrial and port district of Hamburg, Germany, located within the borough of Hamburg-Mitte.
-
D.
Baltschieder
Baltschieder is a small Swiss municipality in the canton of Valais, located in the Upper Valais region of the Alps.
-
E.
Uttendorf
Uttendorf is a village in the Austrian state of Salzburg, known as a base for outdoor activities in the Hohe Tauern region and situated beneath the prominent Hoher Tenn mountain.
- 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.