Triple

T13114111
Position Surface form Disambiguated ID Type / Status
Subject Vorpommern-Greifswald E311048 entity
Predicate contains P35 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: [Vorpommern-Greifswald, contains, Anklam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anklam
Context triple: [Vorpommern-Greifswald, contains, 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9817f8ee8819084078b4bec5e4f18 completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e28105c481908781775ba489c296 completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:06 p.m.