Triple

T3690678
Position Surface form Disambiguated ID Type / Status
Subject Oberhavel E78334 entity
Predicate hasMunicipality P847 FINISHED
Object Hennigsdorf E213861 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: Hennigsdorf | Statement: [Oberhavel, hasMunicipality, Hennigsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hennigsdorf
Context triple: [Oberhavel, hasMunicipality, Hennigsdorf]
  • A. Hennigsdorf chosen
    Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
  • B. Hubersdorf
    Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
  • C. Hermsdorf
    Hermsdorf is a residential locality in the Berlin borough of Reinickendorf, known for its green surroundings and village-like character on the city’s northern edge.
  • D. Heringsdorf
    Heringsdorf is a seaside resort town on the Baltic Sea coast of the island of Usedom in northeastern Germany, known for its historic pier and spa architecture.
  • E. Friedrichsdorf
    Friedrichsdorf is a town in the German state of Hesse, located north of Frankfurt and known historically for its Huguenot heritage and proximity to the Taunus mountains.
  • 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_69ad85e285a081908f8cbfa9e2ed9b75 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4e6147c8190ae358e8cc94f479c completed March 8, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c688e0c8190a7e9ea3fe010c361 completed March 14, 2026, 8:29 a.m.
Created at: March 8, 2026, 3:26 p.m.