Triple

T21650764
Position Surface form Disambiguated ID Type / Status
Subject Martinsried E534329 entity
Predicate hasNearbyMunicipality P4647 FINISHED
Object Planegg NE NERFINISHED

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: Planegg | Statement: [Martinsried, hasNearbyMunicipality, Planegg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Planegg
Context triple: [Martinsried, hasNearbyMunicipality, Planegg]
  • A. Planegg chosen
    Planegg is a municipality in the district of Munich in Bavaria, Germany, known for its scenic location along the Würm River and its proximity to the city of Munich.
  • B. Trostberg
    Trostberg is a small Bavarian town in southeastern Germany known for its historic old town and chemical industry.
  • C. Regenstauf
    Regenstauf is a market town in the Upper Palatinate region of Bavaria, Germany, situated north of the city of Regensburg along the river Regen.
  • D. Nassfeld
    Nassfeld is a major ski and alpine resort area in the Austrian Alps, known for its extensive slopes and modern winter sports facilities.
  • E. Dornstadt
    Dornstadt is a municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, located near the city of Ulm.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5914a3f88190b797188eba34edd8 completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:35 p.m.