Triple
T4365197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelm Bittrich |
E98753
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bittrich |
E98753
|
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: Bittrich | Statement: [Wilhelm Bittrich, familyName, Bittrich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bittrich Context triple: [Wilhelm Bittrich, familyName, Bittrich]
-
A.
Bittrich
chosen
Bittrich is a German surname most notably borne by Wilhelm Bittrich, a high-ranking Waffen-SS commander during World War II.
-
B.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
C.
Trezzini
Trezzini is an Italian-origin surname most notably associated with Domenico Trezzini, the Swiss-Italian architect who helped shape early 18th-century Saint Petersburg.
-
D.
Hitzacker
Hitzacker is a small historic town in Lower Saxony, Germany, known for its picturesque setting on the Elbe River and its traditional half-timbered architecture.
-
E.
Düppel
Düppel is a World War II-era radar countermeasure consisting of clouds of metallic strips or chaff released from aircraft to confuse enemy radar systems.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351fea3e88190807b99868982c491 |
completed | March 12, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5dbcbbd1881908eb9f0ea6b2fe16b |
completed | March 14, 2026, 10:06 p.m. |
Created at: March 12, 2026, 11:17 p.m.