Triple

T14295414
Position Surface form Disambiguated ID Type / Status
Subject Northern Berlin E354425 entity
Predicate hasPart P35 FINISHED
Object Frohnau E1056393 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: Frohnau | Statement: [Northern Berlin, hasPart, Frohnau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frohnau
Context triple: [Northern Berlin, hasPart, Frohnau]
  • A. Frohnau chosen
    Frohnau is a residential district in northern Berlin known for its garden city layout and good public transport connections.
  • B. Roßdorf
    Roßdorf is a municipality in the German state of Hesse, located near the city of Darmstadt.
  • C. Wilmersdorf
    Wilmersdorf is a residential district in southwestern Berlin known for its affluent neighborhoods, shopping streets like Kurfürstendamm, and a mix of historic and modern architecture.
  • D. Friedrichsfelde
    Friedrichsfelde is a residential district in the Berlin borough of Lichtenberg, known for its large housing estates and proximity to Tierpark Berlin.
  • E. Schönewalde
    Schönewalde is a town in the state of Brandenburg, Germany, known for hosting a German Air Force base.
  • 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_69d8278e17088190b328c5a9d4be74ff completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de717b35ec81908968994e65737c66 completed April 14, 2026, 4:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf06f22148190a750a012397b2c68 completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:11 a.m.