Triple

T19514702
Position Surface form Disambiguated ID Type / Status
Subject Innere Stadt E488246 entity
Predicate borderedBy P224 FINISHED
Object Wieden 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: Wieden | Statement: [Innere Stadt, borderedBy, Wieden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wieden
Context triple: [Innere Stadt, borderedBy, Wieden]
  • A. Wieden chosen
    Wieden is the 4th municipal district of Vienna, Austria, known for its historic architecture, cultural institutions, and central urban character.
  • B. Schwechat
    Schwechat is an Austrian town just southeast of Vienna, best known as the site of Vienna International Airport and a major hub for industry and transport.
  • C. Waldstetten
    Waldstetten is a small municipality in the German state of Baden-Württemberg, known for its scenic Swabian Alb surroundings and local rural character.
  • D. Riehen
    Riehen is a municipality in the canton of Basel-Stadt in northern Switzerland, known as a residential suburb of Basel near the German border.
  • E. Seibersdorf
    Seibersdorf is an Austrian town known for hosting major research and testing laboratories of the International Atomic Energy Agency.
  • 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_69d8e8da8bec819081f400199491ccc3 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6359a7070819099d925447c80bf23 completed April 20, 2026, 2:18 p.m.
Created at: April 10, 2026, 1:40 p.m.