Triple
T9208388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Weilheim-Schongau |
E221046
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Seeshaupt |
E215210
|
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: Seeshaupt | Statement: [District of Weilheim-Schongau, containsMunicipality, Seeshaupt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seeshaupt Context triple: [District of Weilheim-Schongau, containsMunicipality, Seeshaupt]
-
A.
Seeshaupt
chosen
Seeshaupt is a Bavarian municipality and lakeside village known for its scenic location at the southern end of Lake Starnberg in southern Germany.
-
B.
Freyung
Freyung is a small town in southeastern Bavaria, Germany, known as a gateway to the Bavarian Forest region.
-
C.
Obergartzem
Obergartzem is a village in the town of Mechernich in North Rhine-Westphalia, western Germany.
-
D.
Seckbach
Seckbach is a district in the east of Frankfurt am Main, Germany, known for its residential character and proximity to green spaces like the Lohrberg.
-
E.
Seelenberg
Seelenberg is a small village that forms one of the local subdivisions of the municipality of Schmitten in Germany.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b217008190a0ab4971dd4a8899 |
completed | April 1, 2026, 8:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b1adc2508190b8a24510ee61f092 |
completed | April 4, 2026, 6:37 a.m. |
Created at: March 30, 2026, 7:26 p.m.