Triple
T17985036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göschenen |
E430208
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Wassen |
—
|
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: Wassen | Statement: [Göschenen, hasRoadConnectionTo, Wassen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wassen Context triple: [Göschenen, hasRoadConnectionTo, Wassen]
-
A.
Wassen
chosen
Wassen is a small Swiss village in the canton of Uri, known for its picturesque church and location along the Gotthard railway and road routes in the central Alps.
-
B.
Nissewaard
Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
-
C.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
D.
Wassenaar
Wassenaar is an affluent coastal town in the western Netherlands known for its wooded estates, beaches, and role as a residential area for diplomats and expatriates.
-
E.
Woudwetering
Woudwetering is a Dutch waterway in South Holland that serves as an important local canal near the village of Woubrugge.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29a27b081909a128a6b978eabf8 |
completed | April 19, 2026, 10:46 a.m. |
Created at: April 10, 2026, 10:23 a.m.