Triple
T16561018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraichgau |
E402336
|
entity |
| Predicate | drainedBy |
P165
|
FINISHED |
| Object | Elsenz |
E384950
|
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: Elsenz | Statement: [Kraichgau, drainedBy, Elsenz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elsenz Context triple: [Kraichgau, drainedBy, Elsenz]
-
A.
Elsenz
chosen
The Elsenz is a river in southwestern Germany that flows through the Kraichgau region before joining the Neckar.
-
B.
Lunzenau
Lunzenau is a small town in the German state of Saxony, known for its location along the Zwickauer Mulde river and its historic architecture.
-
C.
Elze
Elze is a small town in Lower Saxony, Germany, known for its rural character and location within the Hildesheim region.
-
D.
Zernien
Zernien is a municipality in Lower Saxony, Germany, situated within the collective municipality (Samtgemeinde) of Elbtalaue.
-
E.
Sennfeld
Sennfeld is a municipality in the Schweinfurt district of Bavaria, Germany, known for its traditional Franconian character and proximity to the city of Schweinfurt.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576d88288190b33543bea4706a36 |
completed | April 18, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067be809c81909c93eb1253fbf8e5 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.