Triple
T6957737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Rhine |
E161287
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Rheinfelden |
E440023
|
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: Rheinfelden | Statement: [High Rhine, hasPart, Rheinfelden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rheinfelden Context triple: [High Rhine, hasPart, Rheinfelden]
-
A.
Rheinfelden (Aargau)
chosen
Rheinfelden (Aargau) is a historic Swiss town on the Rhine in the canton of Aargau, known as one of the country’s oldest Zähringer-founded cities and a former Habsburg stronghold.
-
B.
Riehe
Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
-
C.
Rheinfelden (Baden)
Rheinfelden (Baden) is a German town in the state of Baden-Württemberg, located on the Rhine near the Swiss border opposite the Swiss town of Rheinfelden.
-
D.
Rüthen
Rüthen is a small historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and location in the scenic Sauerland region.
-
E.
Adliswil
Adliswil is a municipality in the canton of Zurich, Switzerland, situated in the Sihl Valley just south of the city of Zurich.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dad0e52081908b524dc6a66bab01 |
completed | March 27, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7588e2c5c8190a66a0205f3c2bf99 |
completed | March 28, 2026, 4:26 a.m. |
Created at: March 27, 2026, 2:29 p.m.