Triple

T3381278
Position Surface form Disambiguated ID Type / Status
Subject U6 E71188 entity
Predicate terminusNorth P3375 FINISHED
Object Alt-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: Alt-Tegel | Statement: [U6, terminusNorth, Alt-Tegel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alt-Tegel
Context triple: [U6, terminusNorth, Alt-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. Schönefeld
    Schönefeld is a municipality just southeast of Berlin in the German state of Brandenburg, known for hosting the Berlin Brandenburg Airport.
  • E. Munich Airport
    Munich Airport is a major international aviation hub in Bavaria, Germany, serving as one of the country’s busiest airports and a key base for Lufthansa.
  • 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_69ad85a7f80c8190a05e43013f298942 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb5e9af608190bfb228ef99a87bb7 completed March 8, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3344f9b448190aab1038ead60fa48 completed March 12, 2026, 9:46 p.m.
Created at: March 8, 2026, 3:14 p.m.