Triple

T16997934
Position Surface form Disambiguated ID Type / Status
Subject Tegel waterfront E412364 entity
Predicate locatedIn P40 FINISHED
Object Tegel E2522 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: Tegel | Statement: [Tegel waterfront, locatedIn, Tegel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tegel
Context triple: [Tegel waterfront, locatedIn, Tegel]
  • A. Tegel chosen
    Tegel is a locality in the Reinickendorf borough of Berlin, Germany, historically known for its manor associated with the Humboldt family and later for the former Berlin Tegel Airport.
  • B. Schönefeld
    Schönefeld is a municipality just southeast of Berlin in the German state of Brandenburg, known for hosting the Berlin Brandenburg Airport.
  • C. Tempelhof Airport
    Tempelhof Airport is a historic Berlin airfield best known as a central hub of the Berlin Airlift during the Cold War.
  • D. Tempelhof
    Tempelhof is a historic district in Berlin, Germany, best known for the former Tempelhof Airport and its vast airfield now used as a public park.
  • E. Berlin Schönefeld Airport
    Berlin Schönefeld Airport was Berlin’s former secondary international airport located southeast of the city, which was eventually incorporated into the new Berlin Brandenburg Airport complex.
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d37c16d081908ea5e25c992cb254 completed April 18, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01233134288190bbe151f257150dfb completed May 11, 2026, 12:30 a.m.
Created at: April 10, 2026, 5:32 a.m.