Triple

T16536306
Position Surface form Disambiguated ID Type / Status
Subject Stendal E401699 entity
Predicate governingBody P46 FINISHED
Object Stendal town council E401699 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: Stendal town council | Statement: [Stendal, governingBody, Stendal town council]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stendal town council
Context triple: [Stendal, governingBody, Stendal town council]
  • A. Stendal chosen
    Stendal is a historic town in the German state of Saxony-Anhalt, known as a regional cultural center and the birthplace of art historian Johann Joachim Winckelmann.
  • B. Stedesdorf
    Stedesdorf is a small municipality in Lower Saxony, Germany, situated in the East Frisian region.
  • C. Stahnsdorf
    Stahnsdorf is a municipality in the Potsdam-Mittelmark district of Brandenburg, Germany, known for its large forest cemetery and its location on the southwestern outskirts of Berlin.
  • D. Stendal district
    Stendal district is a rural administrative district in the north of the German state of Saxony-Anhalt, known for its historic towns and location along the Elbe River.
  • E. Staßfurt
    Staßfurt is a town in Saxony-Anhalt, Germany, historically known for its salt mining and chemical industry.
  • 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_69d88384bc30819084229e7dcdc39a41 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e34558ec448190a6dcc15d62d1889c completed April 18, 2026, 8:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006094dee481908757b84c10d0dc19 completed May 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 5:15 a.m.