Triple

T3381703
Position Surface form Disambiguated ID Type / Status
Subject Berlin Tegel Airport E71199 entity
Predicate servedCity P3936 FINISHED
Object Magdeburg E240455 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: Magdeburg | Statement: [Berlin Tegel Airport, servedCity, Magdeburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Magdeburg
Context triple: [Berlin Tegel Airport, servedCity, Magdeburg]
  • A. Magdeburg chosen
    Magdeburg is a historic city in central Germany, known for its medieval cathedral, role as a major trading and industrial center, and location on the Elbe River.
  • B. Leipzig
    Leipzig is a major city in eastern Germany known for its rich cultural heritage, vibrant music and arts scene, and important role in trade and commerce.
  • C. Erfurt
    Erfurt is a historic German city in the state of Thuringia, known for its well-preserved medieval old town and as an important cultural and educational center.
  • D. Cottbus
    Cottbus is a city in eastern Germany known as a regional center for science and technology, including aerospace research.
  • E. Schwerin
    Schwerin is a historic city in northern Germany known for its picturesque lakeside setting and landmark Schwerin Castle.
  • 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_69ad85a8fd9c819095ecedf838d2bf1b 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_69be43705d708190abea669829ef2970 completed March 21, 2026, 7:06 a.m.
Created at: March 8, 2026, 3:14 p.m.