Triple
T40735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf Hitler |
E804
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hitler |
E804
|
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: Hitler | Statement: [Adolf Hitler, familyName, Hitler]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hitler Context triple: [Adolf Hitler, familyName, Hitler]
-
A.
Adolf Hitler
chosen
Adolf Hitler was the dictator of Nazi Germany whose aggressive expansionism and genocidal policies led to World War II and the Holocaust.
-
B.
HeinrichHimmler
Heinrich Himmler was a leading Nazi official who headed the SS and was one of the principal architects and overseers of the Holocaust.
-
C.
Julius Streicher
Julius Streicher was a prominent Nazi propagandist and publisher of the antisemitic newspaper Der Stürmer who was convicted of crimes against humanity at the Nuremberg trials.
-
D.
ReinhardHeydrich
Reinhard Heydrich was a high-ranking Nazi SS and police official, one of the main architects of the Holocaust and a key organizer of the regime’s genocidal policies.
-
E.
Adolf Eichmann
Adolf Eichmann was a high-ranking Nazi SS officer who played a central administrative role in organizing the logistics of the Holocaust.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24adf3640819095576e072fb5d9a8 |
completed | Feb. 28, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a332c400788190bb9beca3246bcf46 |
completed | Feb. 28, 2026, 6:24 p.m. |
Created at: Feb. 28, 2026, 1:46 a.m.