Triple

T18192169
Position Surface form Disambiguated ID Type / Status
Subject Eisenacher Straße E435563 entity
Predicate locatedIn P40 FINISHED
Object Schöneberg 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: Schöneberg | Statement: [Eisenacher Straße, locatedIn, Schöneberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schöneberg
Context triple: [Eisenacher Straße, locatedIn, Schöneberg]
  • A. Schöneberg chosen
    Schöneberg is a district of Berlin, Germany, historically notable as the site of John F. Kennedy’s famous “Ich bin ein Berliner” speech.
  • B. Schönewalde
    Schönewalde is a town in the state of Brandenburg, Germany, known for hosting a German Air Force base.
  • C. Schönholz
    Schönholz is a locality in Berlin, Germany, served by the city’s S-Bahn rapid transit network.
  • D. Petershagen
    Petershagen is a small town in North Rhine-Westphalia, Germany, known for its historic architecture and scenic location along the Weser River.
  • E. Schönwalde
    Schönwalde is a locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d05974819094b4a50d081be881 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.