Triple

T9941079
Position Surface form Disambiguated ID Type / Status
Subject Ernst Beyeler E194081 entity
Predicate workLocation P7 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: [Ernst Beyeler, workLocation, Riehen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riehen
Context triple: [Ernst Beyeler, workLocation, 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. Vaterstetten
    Vaterstetten is a municipality in the district of Ebersberg near Munich in Bavaria, Germany, known as a residential suburb with strong transport links to the Bavarian capital.
  • C. Sulzach
    Sulzach is a small river in Bavaria, Germany, that flows through the town of Feuchtwangen and forms part of the local Franconian river system.
  • D. Ranshofen
    Ranshofen is a district of the town of Braunau am Inn in Upper Austria, known historically for its industrial facilities and its location near the German border.
  • E. Neuötting
    Neuötting is a small Bavarian town in southeastern Germany known for its historic town center and location near the Austrian border.
  • 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_69ca82e409348190a393777356b80a2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb60f4ffc8190bfe916bb4a7bf5c5 completed April 2, 2026, 12:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b5d295908190a064fb72d65b6e24 completed April 5, 2026, 7:19 p.m.
Created at: March 30, 2026, 8:44 p.m.