Triple
T12877922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig metropolitan region |
E308012
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Seelitz |
E713393
|
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: Seelitz | Statement: [Leipzig metropolitan region, containsCity, Seelitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seelitz Context triple: [Leipzig metropolitan region, containsCity, Seelitz]
-
A.
Seelitz
chosen
Seelitz is a municipality in the Free State of Saxony in eastern Germany, known for its rural character and location within the Mittelsachsen region.
-
B.
Langendorf
Langendorf is a municipality in the Weißenfels area of Saxony-Anhalt in eastern Germany.
-
C.
Langendorf
Langendorf is a municipality in the canton of Solothurn in northwestern Switzerland.
-
D.
Blasewitz
Blasewitz is a historic and affluent district of Dresden, Germany, known for its riverside villas and location along the Elbe River.
-
E.
Dennewitz
Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
- 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_69f6c0e54dc48190acf120ca5fe516ab |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 9, 2026, 5:38 p.m.