Triple

T13635029
Position Surface form Disambiguated ID Type / Status
Subject Bad Schandau E325825 entity
Predicate hasSubdivision P747 FINISHED
Object Ostrau E709518 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: Ostrau | Statement: [Bad Schandau, hasSubdivision, Ostrau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostrau
Context triple: [Bad Schandau, hasSubdivision, Ostrau]
  • A. Ostrau chosen
    Ostrau is a municipality in the German state of Saxony, located within the administrative region of Mittelsachsen.
  • B. Vishnevo
    Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
  • C. Dzerzhinovo
    Dzerzhinovo is a village in present-day Belarus best known as the birthplace of Soviet statesman and secret police founder Felix Dzerzhinsky.
  • D. Krasnystaw
    Krasnystaw is a town in eastern Poland known for its agricultural surroundings and annual Chmielaki beer and hops festival.
  • E. Plavsk
    Plavsk is a small town in western Russia known for its agricultural surroundings and location within the Tula region.
  • 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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc5a616dc81908b8c1213e1d4beed completed April 12, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69f794307c288190a0f4629bf5e2b0d9 completed May 3, 2026, 6:30 p.m.
Created at: April 9, 2026, 9:51 p.m.