Triple
T12877787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig metropolitan region |
E308012
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Zwenkau |
E190257
|
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: Zwenkau | Statement: [Leipzig metropolitan region, containsCity, Zwenkau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zwenkau Context triple: [Leipzig metropolitan region, containsCity, Zwenkau]
-
A.
Zwenkau
chosen
Zwenkau is a small town in the Free State of Saxony in eastern Germany, situated near Leipzig and known for its proximity to former lignite mining areas now being transformed into lake landscapes.
-
B.
Zernien
Zernien is a municipality in Lower Saxony, Germany, situated within the collective municipality (Samtgemeinde) of Elbtalaue.
-
C.
Kornhain
Kornhain is a village-level subdivision of the town of Wurzen in the German state of Saxony.
-
D.
Witellikon
Witellikon is a small settlement within the municipality of Küsnacht in the canton of Zürich, Switzerland, situated along the shores of Lake Zurich.
-
E.
Schlenze
Schlenze is a small river in central Germany, known as a tributary of the Saale flowing through the state of Saxony-Anhalt.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d970fa8474819086a8af3c90f3ca84 |
completed | April 10, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69bb83bac8190838f7537b806317c |
completed | May 3, 2026, 12:50 a.m. |
Created at: April 9, 2026, 5:38 p.m.