Triple

T8747446
Position Surface form Disambiguated ID Type / Status
Subject Braunschweig-Wolfsburg Airport E207867 entity
Predicate serves P98 FINISHED
Object Wolfsburg E74139 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: Wolfsburg | Statement: [Braunschweig-Wolfsburg Airport, serves, Wolfsburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wolfsburg
Context triple: [Braunschweig-Wolfsburg Airport, serves, Wolfsburg]
  • A. Wolfsburg chosen
    Wolfsburg is a German city best known as the headquarters and main production site of the Volkswagen automobile company.
  • B. Dortmund
    Dortmund is a major city in western Germany known for its rich football culture, industrial heritage, and home club Borussia Dortmund.
  • C. Mönchengladbach
    Mönchengladbach is a city in western Germany known for its textile industry heritage and its football club Borussia Mönchengladbach.
  • D. Nottuln
    Nottuln is a historic municipality in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
  • E. Ingolstadt
    Ingolstadt is a historic city in southern Germany known for its medieval architecture, university tradition, and role as a major hub of the automotive industry.
  • 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_69ca835bb2bc819084bb5906cb6ef7f8 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5da2d67c819094b2b39c78384d0d completed March 31, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6f0524e08190bc5ba6cda2e2e4fa completed April 3, 2026, 7:40 a.m.
Created at: March 30, 2026, 6:39 p.m.