Triple
T1469209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alois Hitler |
E27095
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Schicklgruber |
E166859
|
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: Schicklgruber | Statement: [Alois Hitler, familyName, Schicklgruber]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schicklgruber Context triple: [Alois Hitler, familyName, Schicklgruber]
-
A.
Alois Schicklgruber
chosen
Alois Schicklgruber, later known as Alois Hitler, was an Austrian customs official best known as the father of Nazi dictator Adolf Hitler.
-
B.
Franz
Franz is the given name of Franz Cardinal König, a prominent 20th-century Austrian Catholic cardinal and influential church leader.
-
C.
Oskar
Oskar is a masculine given name of Germanic origin, commonly used in various European countries.
-
D.
Maria Schicklgruber
Maria Schicklgruber was an Austrian peasant woman best known as the paternal grandmother of Adolf Hitler.
-
E.
Jozef
Jozef is a masculine given name of Hebrew origin, commonly used in Central and Eastern Europe as a variant of Joseph.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d8bb68819095b7b413247ad657 |
completed | March 1, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58b0be2c8190993a5b4592acf7d2 |
completed | March 8, 2026, 11:08 a.m. |
Created at: March 1, 2026, 8:01 p.m.