Triple

T1121681
Position Surface form Disambiguated ID Type / Status
Subject Tegel Manor E24625 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 Manor, locatedIn, Tegel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tegel
Context triple: [Tegel Manor, 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. Tempelhof Airport
    Tempelhof Airport is a historic Berlin airfield best known as a central hub of the Berlin Airlift during the Cold War.
  • C. Berlin Brandenburg Airport
    Berlin Brandenburg Airport is the main international airport serving Germany’s capital region, designed to replace and consolidate Berlin’s former commercial airports.
  • D. Hannover Airport
    Hannover Airport is an international airport serving the city of Hanover in northern Germany, handling passenger and cargo flights for the region.
  • E. Nuremberg Airport
    Nuremberg Airport is an international airport in northern Bavaria, Germany, serving the city of Nuremberg and the surrounding Franconia region with passenger and cargo flights.
  • 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_69a4940712c88190aa244f3fc6070a65 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bbbf71188190b82c8fff9d5ac01a completed March 1, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac539d51848190a9eb9ddaa7e4c6a8 completed March 7, 2026, 4:34 p.m.
Created at: March 1, 2026, 7:44 p.m.