Triple

T21353791
Position Surface form Disambiguated ID Type / Status
Subject Bitche canton E526557 entity
Predicate contains P35 FINISHED
Object Goetzenbruck 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: Goetzenbruck | Statement: [Bitche canton, contains, Goetzenbruck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goetzenbruck
Context triple: [Bitche canton, contains, Goetzenbruck]
  • A. Goetzenbruck chosen
    Goetzenbruck is a small commune in northeastern France’s Moselle department, historically known for its glassmaking industry and location within the Pays de Bitche region.
  • B. Beutelsbach
    Beutelsbach is a small municipality in the rural Passau district of Lower Bavaria in southeastern Germany.
  • C. Hersbruck
    Hersbruck is a small historic town in the Franconian region of Bavaria, Germany, known for its picturesque setting in the Pegnitz Valley and traditional Bavarian architecture.
  • D. Burbach
    Burbach is a municipality in the district of Siegen-Wittgenstein in the German state of North Rhine-Westphalia.
  • E. Burbach
    Burbach is a district of the city of Saarbrücken in the German federal state of Saarland.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5bac9e1481909121e89f046c77f6 completed April 26, 2026, 6:38 p.m.
Created at: April 16, 2026, 5:05 p.m.