Triple
T16482099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chur–Rorschach railway line |
E400344
|
entity |
| Predicate | servesTown |
P847
|
FINISHED |
| Object | Goldach |
E1019270
|
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: Goldach | Statement: [Chur–Rorschach railway line, servesTown, Goldach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goldach Context triple: [Chur–Rorschach railway line, servesTown, Goldach]
-
A.
Goldach
chosen
Goldach is a municipality in northeastern Switzerland, located on the southern shore of Lake Constance in the canton of St. Gallen.
-
B.
Haslach
Haslach is a district or locality that forms part of the town of Oberkirch in the German state of Baden-Württemberg.
-
C.
Haslach
Haslach is a town in southern Germany historically noted as the site of the Battle of Haslach-Jungingen during the Napoleonic Wars.
-
D.
Hasslach
The Hasslach is a river in Bavaria, Germany, that flows through the town of Kronach and is part of the Main river basin.
-
E.
Seckbach
Seckbach is a district in the east of Frankfurt am Main, Germany, known for its residential character and proximity to green spaces like the Lohrberg.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e03643881908b16ddb9004af5d0 |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bafe159c8190b66d2cd21b8ddb88 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:13 a.m.