Triple
T19715432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herzogtum Lauenburg district |
E473463
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Lauenburg/Elbe |
E155306
|
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: Lauenburg/Elbe | Statement: [Herzogtum Lauenburg district, hasMunicipality, Lauenburg/Elbe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lauenburg/Elbe Context triple: [Herzogtum Lauenburg district, hasMunicipality, Lauenburg/Elbe]
-
A.
Elbsche
Elbsche is a small river in North Rhine-Westphalia, Germany, that flows through the city of Witten and its surrounding region.
-
B.
Teltow
Teltow is a town in the German state of Brandenburg, located just southwest of Berlin and known for its historical core and proximity to the capital.
-
C.
Aussig an der Elbe
Aussig an der Elbe is the German name for the Czech industrial and port city of Ústí nad Labem, located on the Elbe River in northern Bohemia.
-
D.
Lauenburg
chosen
Lauenburg is a historic town in northern Germany situated on the banks of the Elbe River.
-
E.
Gadebusch
Gadebusch is a small historic town in northern Germany known for its medieval architecture and rural surroundings.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440cb47c81908124dfbd6f781d23 |
completed | April 20, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07aba0a8948190afc7a943ba17b4a2 |
completed | May 15, 2026, 11:26 p.m. |
Created at: April 10, 2026, 1:46 p.m.