Triple
T12917296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Tölz-Wolfratshausen |
E309018
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Münsing |
E219467
|
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: Münsing | Statement: [Bad Tölz-Wolfratshausen, hasPart, Münsing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Münsing Context triple: [Bad Tölz-Wolfratshausen, hasPart, Münsing]
-
A.
Münsing
chosen
Münsing is a municipality in Bavaria, Germany, located near Lake Starnberg and known for its scenic rural landscape and proximity to the Alps.
-
B.
Münnich
Münnich is a German-language surname borne by various notable individuals, including Hungarian communist politician Ferenc Münnich.
-
C.
Münsingen
Münsingen is a Swiss municipality in the canton of Bern, known for its scenic location in the Aare valley between Bern and Thun.
-
D.
Lorsbach
Lorsbach is a district of the town Hofheim am Taunus in the German state of Hesse, situated in the Taunus mountain region.
-
E.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a571a3e48190a32d362adc6eaee2 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:41 p.m.