Triple

T11923846
Position Surface form Disambiguated ID Type / Status
Subject Meylan E283730 entity
Predicate hasTwinTown P919 FINISHED
Object Planegg E960016 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: Planegg | Statement: [Meylan, hasTwinTown, Planegg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Planegg
Context triple: [Meylan, hasTwinTown, 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. Dornstadt
    Dornstadt is a municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, located near the city of Ulm.
  • E. Pocking
    Pocking is a small town in southeastern Bavaria, Germany, known for its proximity to the Austrian border and the spa region around Bad Füssing.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e8e2fc648190a446c1917db1c7d9 completed April 10, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49ce47d488190af7f832e7719a4ce completed May 1, 2026, 12:30 p.m.
Created at: April 8, 2026, 9:45 p.m.