Triple
T15204310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Wolfrum |
E363348
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Schlaifhausen |
E1194691
|
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: Schlaifhausen | Statement: [Walter Wolfrum, residence, Schlaifhausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schlaifhausen Context triple: [Walter Wolfrum, residence, Schlaifhausen]
-
A.
Schlaifhausen
chosen
Schlaifhausen is a small village in Bavaria, Germany, known as the birthplace of Luftwaffe fighter ace Walter Wolfrum.
-
B.
Helmarshausen
Helmarshausen is a historic district of the spa town Bad Karlshafen in northern Hesse, Germany, known for its medieval heritage and former Benedictine monastery.
-
C.
Balzhausen
Balzhausen is a small municipality in the Bavarian region of Swabia in southern Germany.
-
D.
Deisenhausen
Deisenhausen is a small municipality in the Bavarian region of Swabia in southern Germany.
-
E.
Schneppenhausen
Schneppenhausen is a village and district of the town of Weiterstadt in the German state of Hesse.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff78dab488190a89b9eb4f648b36c |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 3:11 a.m.