Triple
T20200097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egg an der Günz |
E493190
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Babenhausen (Swabia) |
—
|
NE NERFINISHED |
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: Babenhausen (Swabia) | Statement: [Egg an der Günz, locatedNear, Babenhausen (Swabia)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Babenhausen (Swabia) Context triple: [Egg an der Günz, locatedNear, Babenhausen (Swabia)]
-
A.
Babenhausen
chosen
Babenhausen is a market town in the Unterallgäu district of Bavaria, Germany, known for its historic center and role as a local administrative and service hub.
-
B.
Babenhausen
Babenhausen is a small town in the German state of Hesse, known for its historic old town and location southeast of Frankfurt am Main.
-
C.
Bebenhausen
Bebenhausen is a historic village in Baden-Württemberg, Germany, best known for its well-preserved former Cistercian monastery and royal hunting lodge.
-
D.
Berghausen
Berghausen is a village in the Karlsruhe district of Baden-Württemberg, Germany, situated along the Pfinz river.
-
E.
Berghausen
Berghausen is a district of the town of Langenfeld in the Rhineland region of North Rhine-Westphalia, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d8d01648190b1b3a6e03f0258d8 |
completed | April 20, 2026, 6:16 p.m. |
Created at: April 11, 2026, 11:37 p.m.