Triple
T17599282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Ohlendorf |
E428651
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ohlendorf |
—
|
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: Ohlendorf | Statement: [Otto Ohlendorf, familyName, Ohlendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ohlendorf Context triple: [Otto Ohlendorf, familyName, Ohlendorf]
-
A.
Ohlendorf
chosen
Ohlendorf is a German surname most notably associated with Otto Ohlendorf, a high-ranking Nazi SS officer and war criminal.
-
B.
Fritzdorf
Fritzdorf is a village in the municipality of Wachtberg in North Rhine-Westphalia, Germany.
-
C.
Kasendorf
Kasendorf is a small municipality in the Upper Franconia region of Bavaria, Germany, known for its rural character and scenic surroundings.
-
D.
Wechmar
Wechmar is a village in Thuringia, Germany, historically notable as the ancestral home of the Bach musical family.
-
E.
Baerenthal
Baerenthal is a small village in northeastern France’s Moselle department, known for its forested landscapes and location within the Pays de Bitche region.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.