Triple

T9582738
Position Surface form Disambiguated ID Type / Status
Subject Abbey of Gengenbach E231212 entity
Predicate locatedIn P40 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: [Abbey of Gengenbach, locatedIn, Gengenbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gengenbach
Context triple: [Abbey of Gengenbach, locatedIn, 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. Beutelsbach
    Beutelsbach is a small municipality in the rural Passau district of Lower Bavaria in southeastern Germany.
  • D. Orisbach
    Orisbach is a small stream in Switzerland that serves as a tributary of the Ergolz River in the canton of Basel-Landschaft.
  • E. Obergoms
    Obergoms is a municipality in the canton of Valais in southwestern Switzerland, known for its high Alpine landscapes and traditional mountain villages.
  • 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_69ca848161688190a68d514a0a9d5129 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99cd59008190888eb11f00f61994 completed April 1, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcaf94608190992124965a805228 completed April 5, 2026, 1:36 a.m.
Created at: March 30, 2026, 8:05 p.m.