Triple
T20466448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seeham |
E502061
|
entity |
| Predicate | hasShoreOn |
P26435
|
FINISHED |
| Object | Obertrumer See |
—
|
NE NERFINISHED |
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: Obertrumer See | Statement: [Seeham, hasShoreOn, Obertrumer See]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Obertrumer See Context triple: [Seeham, hasShoreOn, Obertrumer See]
-
A.
Obertrumer See
chosen
Obertrumer See is a scenic lake in the Salzburg region of Austria, popular for swimming, boating, and other recreational activities.
-
B.
Kummerower See
Kummerower See is a large lake in northeastern Germany, known for its natural landscapes, water sports, and role as a popular recreational area within the Mecklenburg Lake District.
-
C.
Waginger See
Waginger See is a warm, scenic lake in southeastern Bavaria, Germany, popular for swimming, water sports, and tourism in the Chiemgau region.
-
D.
Ostorfer See
Ostorfer See is a lake in the German state of Mecklenburg-Vorpommern, forming part of the lake landscape around the city of Schwerin.
-
E.
Segeberger See
Segeberger See is a lake in Schleswig-Holstein, northern Germany, known for its scenic surroundings and proximity to the town of Bad Segeberg.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696aa0794819082c9989b1f7e9f37 |
completed | April 20, 2026, 9:12 p.m. |
Created at: April 16, 2026, 11:33 a.m.