Triple
T20718626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linth River |
E509246
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Weesen |
—
|
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: Weesen | Statement: [Linth River, flowsNear, Weesen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weesen Context triple: [Linth River, flowsNear, Weesen]
-
A.
Weesen
chosen
Weesen is a picturesque Swiss lakeside town in the Heidiland holiday region, known for its scenic setting on Lake Walen and access to nearby mountains and outdoor activities.
-
B.
Wusse
Wusse is a small settlement in the German state of Mecklenburg-Vorpommern that serves as the administrative seat of the municipality of Ummanz.
-
C.
Veeweyde
Veeweyde is a neighborhood-level district within the Brussels municipality of Anderlecht, known primarily as a residential area served by the Veeweyde metro station.
-
D.
Weshesh
Weshesh were an obscure ancient group likely associated with the Sea Peoples, known primarily from Egyptian records describing Late Bronze Age conflicts in the eastern Mediterranean.
-
E.
Weisweil
Weisweil is a small municipality in the Waldshut district of the state of Baden-Württemberg in southwestern Germany.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d39bec8190b3642b0d6d833375 |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:25 p.m.