Triple
T1034262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel-Stadt |
E22322
|
entity |
| Predicate | municipality |
P852
|
FINISHED |
| Object | Riehen |
E134855
|
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: Riehen | Statement: [Basel-Stadt, municipality, Riehen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riehen Context triple: [Basel-Stadt, municipality, Riehen]
-
A.
Riehen
chosen
Riehen is a municipality in the canton of Basel-Stadt in northern Switzerland, known as a residential suburb of Basel near the German border.
-
B.
Heidenheim an der Brenz
Heidenheim an der Brenz is a town in the German state of Baden-Württemberg known for its industrial heritage, historic castle Hellenstein, and location on the Brenz River near the Swabian Jura.
-
C.
Stetten
Stetten is a locality within the town of Lichtenfels in the German state of Bavaria.
-
D.
Zuchwil
Zuchwil is a Swiss municipality located near the city of Solothurn in the canton of Solothurn.
-
E.
Rosenheim
Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b814c16c8190ac4d20feecdadbae |
completed | March 1, 2026, 10:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbad55a4c8190977e8e5d313c56df |
completed | March 7, 2026, 11:55 p.m. |
Created at: March 1, 2026, 7:41 p.m.