Triple
T12877780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig metropolitan region |
E308012
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Eilenburg |
E444915
|
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: Eilenburg | Statement: [Leipzig metropolitan region, containsCity, Eilenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eilenburg Context triple: [Leipzig metropolitan region, containsCity, Eilenburg]
-
A.
Eilenburg
chosen
Eilenburg is a small historic town in the German state of Saxony, situated on the Mulde River northeast of Leipzig.
-
B.
Riedenburg
Riedenburg is a small Bavarian town in southern Germany known for its scenic location in the Altmühl Valley and its historic castles.
-
C.
Oranienburg
Oranienburg is a town in Brandenburg, Germany, historically known as the site of the Nazi Sachsenhausen concentration camp.
-
D.
Wurzen
Wurzen is a historic town in the German state of Saxony, known for its medieval architecture and location on the river Mulde east of Leipzig.
-
E.
Lankwitz
Lankwitz is a residential locality in the southwestern part of Berlin, known for its quiet neighborhoods, green spaces, and mix of historic and modern architecture.
- 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_69fdf0683b90819098864f73b6976517 |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 9, 2026, 5:38 p.m.