Triple

T1898717
Position Surface form Disambiguated ID Type / Status
Subject Landsberg am Lech district E37641 entity
Predicate namedAfter P63 FINISHED
Object Landsberg am Lech E82292 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: Landsberg am Lech | Statement: [Landsberg am Lech district, namedAfter, Landsberg am Lech]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Landsberg am Lech
Context triple: [Landsberg am Lech district, namedAfter, Landsberg am Lech]
  • A. Landsberg am Lech chosen
    Landsberg am Lech is a historic Bavarian town in southern Germany known for its medieval old town, picturesque setting on the Lech River, and its association with the nearby Landsberg Prison.
  • B. Landsberg
    Landsberg is a town in the Saalekreis district of the German state of Saxony-Anhalt.
  • C. Neu-Ulm
    Neu-Ulm is a Bavarian town in southern Germany located across the Danube River from the city of Ulm, forming a closely linked urban area with it.
  • D. Rosenheim
    Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
  • E. Traunstein
    Traunstein is a town in southeastern Bavaria, Germany, known as a regional administrative and cultural center near the Chiemsee and 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_69a8861be7148190a680937ec451a304 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb17181b0819090683c55fd1352cb completed March 7, 2026, 5:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5db49ec24819098594c395bc88fe8 completed March 14, 2026, 10:03 p.m.
Created at: March 4, 2026, 7:35 p.m.