Triple

T22319055
Position Surface form Disambiguated ID Type / Status
Subject Wasseramt District E551730 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Zielebach NE NERFINISHED

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: Zielebach | Statement: [Wasseramt District, containsAdministrativeTerritorialEntity, Zielebach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zielebach
Context triple: [Wasseramt District, containsAdministrativeTerritorialEntity, Zielebach]
  • A. Zielebach chosen
    Zielebach is a small municipality in the canton of Bern in Switzerland.
  • B. Weinbach
    Weinbach is a municipality in the Limburg-Weilburg district of the German state of Hesse.
  • C. Seelbach
    Seelbach is a municipality in southwestern Germany’s Baden-Württemberg region, situated in the Ortenau district near the Black Forest.
  • D. Fiescherbach
    Fiescherbach is a mountain stream in the Swiss Alps that flows through the village of Fiesch in the canton of Valais.
  • E. Weisenbach
    Weisenbach is a small municipality in southwestern Germany, located in the Black Forest region of Baden-Württemberg.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15762fac08190a6a514baffbbbca1 completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:42 p.m.