Triple

T14266564
Position Surface form Disambiguated ID Type / Status
Subject Otto Lilienthal E353659 entity
Predicate birthPlace P1 FINISHED
Object Anklam E213445 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: Anklam | Statement: [Otto Lilienthal, birthPlace, Anklam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anklam
Context triple: [Otto Lilienthal, birthPlace, Anklam]
  • A. Anklam chosen
    Anklam is a small historic town in northeastern Germany’s Mecklenburg-Vorpommern state, known as the birthplace of aviation pioneer Otto Lilienthal.
  • B. Johannisthal
    Johannisthal is a locality in the Berlin borough of Treptow-Köpenick, known historically for Germany’s first airfield and its early aviation activities.
  • C. Wrangelsburg
    Wrangelsburg is a historic estate and locality in northeastern Germany associated with the 17th-century Swedish field marshal and statesman Carl Gustaf Wrangel.
  • D. Galwa
    Galwa is a dialect of the Myene language spoken by communities in Gabon.
  • E. Ankum
    Ankum is a municipality in Lower Saxony, Germany, situated within the Osnabrück district.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6358c2288190ac1fd26e688a605d completed April 14, 2026, 3:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd326551b08190ae8fe220a6422339 completed May 8, 2026, 12:46 a.m.
Created at: April 10, 2026, 1:09 a.m.