Triple

T5301150
Position Surface form Disambiguated ID Type / Status
Subject Ortenaukreis E119983 entity
Predicate containsMunicipality P852 FINISHED
Object Gengenbach E489546 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: Gengenbach | Statement: [Ortenaukreis, containsMunicipality, Gengenbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gengenbach
Context triple: [Ortenaukreis, containsMunicipality, Gengenbach]
  • A. Gengenbach chosen
    Gengenbach is a historic town in Germany’s Black Forest region, known for its well-preserved medieval old town and picturesque half-timbered houses.
  • B. Gernsbach
    Gernsbach is a historic town in southwestern Germany’s Black Forest region, known for its medieval old town and picturesque setting along the Murg River.
  • C. Brackenberg
    Brackenberg is an early recorded historical name for the Brocken, the highest peak in Germany’s Harz Mountains.
  • D. Bissingen
    Bissingen is a suburb of the town of Herbrechtingen in the state of Baden-Württemberg, Germany.
  • E. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • 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_69bd44704be88190acdb2ac481b0ff55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8509f67c8190b2f82a8370301a59 completed March 20, 2026, 5:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf332d0c608190be0c8e740fe216b7 completed March 22, 2026, 12:09 a.m.
Created at: March 20, 2026, 1:53 p.m.