Triple
T20016503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ach (Staffelsee) |
E494733
|
entity |
| Predicate | mouthOfWaterBody |
P3817
|
FINISHED |
| Object | Ammer |
—
|
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: Ammer | Statement: [Ach (Staffelsee), mouthOfWaterBody, Ammer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ammer Context triple: [Ach (Staffelsee), mouthOfWaterBody, Ammer]
-
A.
Ammer
chosen
The Ammer is a river in Bavaria, Germany, known for flowing through the Ammergau Alps and feeding the Ammersee.
-
B.
Ammer
The Ammer is a small river in the German state of Baden-Württemberg that flows through the university town of Tübingen and into the Neckar.
-
C.
Ampen
Ampen is a district or locality within the German town of Soest in North Rhine-Westphalia.
-
D.
Ammerland
Ammerland is a locality within the Bavarian municipality of Münsing in Germany, situated near Lake Starnberg.
-
E.
Hamme
Hamme is a municipality in East Flanders, Belgium, known for its location along the Scheldt River and its blend of residential areas and natural landscapes.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623cb8188190b95913ffed895930 |
completed | April 20, 2026, 5:28 p.m. |
Created at: April 11, 2026, 3:34 p.m.