Triple

T16039968
Position Surface form Disambiguated ID Type / Status
Subject Angermünde E389067 entity
Predicate locatedNear P294 FINISHED
Object Schwedt/Oder E689416 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: Schwedt/Oder | Statement: [Angermünde, locatedNear, Schwedt/Oder]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwedt/Oder
Context triple: [Angermünde, locatedNear, Schwedt/Oder]
  • A. Schwedt (Oder)
    Schwedt (Oder) is a town in northeastern Germany near the Polish border, known for its petrochemical industry and location along the Oder River.
  • B. Schwedt chosen
    Schwedt is a town in northeastern Germany, located on the Oder River near the Polish border, known for its industrial facilities and cross-border regional ties.
  • C. Grömitz
    Grömitz is a Baltic Sea resort town in northern Germany known for its long sandy beaches and seaside tourism.
  • D. Geringswalde
    Geringswalde is a small town in the Free State of Saxony in eastern Germany, known for its rural character and location within the Central Saxon region.
  • E. Lusatian Neisse
    The Lusatian Neisse is a river in Central Europe that flows through the Czech Republic, Germany, and Poland, forming part of the German–Polish border.
  • 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1833f84188190baa3a452df880284 completed April 17, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbd77c5481908644742a8a8f3e68 completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 4:56 a.m.