Triple

T5208339
Position Surface form Disambiguated ID Type / Status
Subject Munich Airport E117566 entity
Predicate locatedNear P294 FINISHED
Object Freising E375515 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: Freising | Statement: [Munich Airport, locatedNear, Freising]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Freising
Context triple: [Munich Airport, locatedNear, Freising]
  • A. Freising chosen
    Freising is a historic Bavarian town near Munich, known for its cathedral hill and one of the world’s oldest operating breweries at Weihenstephan.
  • B. Traunstein
    Traunstein is a town in southeastern Bavaria, Germany, known as a regional administrative and cultural center near the Chiemsee and the Alps.
  • C. Kaufbeuren
    Kaufbeuren is a historic Bavarian town in southern Germany known for its well-preserved medieval old town and traditional Swabian culture.
  • D. Füssen
    Füssen is a picturesque Bavarian town in southern Germany, known for its historic old town, proximity to Neuschwanstein Castle, and scenic location near the Alps.
  • E. Rosenheim
    Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
  • 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_69bd4463dd3c81909966123f20b79d57 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7a6d70d081908c74e86b3bca9ba2 completed March 20, 2026, 4:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f5aca208190824a611c784ab1a1 completed March 28, 2026, 1:31 a.m.
Created at: March 20, 2026, 1:47 p.m.