Triple
T790707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian Plateau |
E16906
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ammersee |
E41332
|
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: Ammersee | Statement: [Bavarian Plateau, contains, Ammersee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ammersee Context triple: [Bavarian Plateau, contains, Ammersee]
-
A.
Ammersee
chosen
Ammersee is a large glacial lake in southern Germany known for its scenic shores, recreational activities, and proximity to the Alps.
-
B.
Starnberger See
Starnberger See is a large, scenic lake in southern Germany known for its affluent lakeside communities, recreational activities, and historical associations with Bavarian royalty.
-
C.
Chiemsee
Chiemsee is one of Germany’s largest lakes, famed for its scenic Alpine setting and historic islands such as Herrenchiemsee with its royal palace.
-
D.
Schluchsee
Schluchsee is a large reservoir and popular recreational lake in Germany’s Black Forest, known for swimming, sailing, and scenic hiking.
-
E.
Tegernsee
Tegernsee is a picturesque alpine lake in southern Germany renowned for its clear waters, surrounding mountains, and popular spa and resort towns.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79754988190ab494b1c54d6a2a4 |
completed | March 1, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7edfae07c8190b104c869302cd486 |
completed | March 4, 2026, 8:31 a.m. |
Created at: March 1, 2026, 7:38 p.m.