Triple
T2927341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Streicher |
E78876
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Fleinhausen |
E86834
|
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: Fleinhausen | Statement: [Julius Streicher, placeOfBirth, Fleinhausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fleinhausen Context triple: [Julius Streicher, placeOfBirth, Fleinhausen]
-
A.
Fleinhausen
chosen
Fleinhausen is a small village in Bavaria, Germany, historically noted as the birthplace of Nazi propagandist Julius Streicher.
-
B.
Wienhausen
Wienhausen is a historic village in Lower Saxony, Germany, best known for its medieval Cistercian nunnery and well-preserved half-timbered architecture.
-
C.
Irschenhausen
Irschenhausen is a small village in Bavaria, Germany, known in part as the place where German field marshal Erich von Manstein died.
-
D.
Rheinhausen
Rheinhausen is a district of the German city of Duisburg, located on the western bank of the Rhine in North Rhine-Westphalia.
-
E.
Gunzenhausen
Gunzenhausen is a historic town in Bavaria, Germany, known for its location on the Altmühl River and as a gateway to the Franconian Lake District.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f3434088190b20889c4e68a9361 |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 8, 2026, 2:55 p.m.