Triple
T7239012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauenburg |
E155306
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Lauenburg |
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 | Statement: [Lauenburg, shortName, Lauenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lauenburg Context triple: [Lauenburg, shortName, Lauenburg]
-
A.
Lauenburg
chosen
Lauenburg is a historic town in northern Germany situated on the banks of the Elbe River.
-
B.
Güstrow
Güstrow is a historic town in northern Germany known for its Renaissance castle, brick Gothic cathedral, and association with sculptor Ernst Barlach.
-
C.
Glücksburg
Glücksburg is a European royal house of German origin that has provided monarchs to several countries, including Denmark, Norway, and Greece.
-
D.
Eutin
Eutin is a historic town in northern Germany’s Schleswig-Holstein region, known for its picturesque lakeside setting, castle, and cultural festivals.
-
E.
Lauenburg in Pommern
Lauenburg in Pommern is a historic town in the former Prussian province of Pomerania, now known as Lębork in northern Poland.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea37fa9081908e9c3abe49d151e5 |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc3d75b48190916bf327396f2666 |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.