Triple

T20046700
Position Surface form Disambiguated ID Type / Status
Subject Groß-Gerau district E497576 entity
Predicate contains P35 FINISHED
Object Trebur 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: Trebur | Statement: [Groß-Gerau district, contains, Trebur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trebur
Context triple: [Groß-Gerau district, contains, Trebur]
  • A. Trebur chosen
    Trebur is a historic municipality in the German state of Hesse, known for its medieval significance within the Holy Roman Empire.
  • B. Montabaur
    Montabaur is a historic town in western Germany’s Rhineland-Palatinate region, known for its distinctive hilltop castle and well-preserved old town.
  • C. Benrath
    Benrath is a German surname most notably associated with the late actor Martin Benrath.
  • D. Benrath
    Benrath is a district of Düsseldorf in western Germany, known for its historic Benrath Palace and surrounding park.
  • E. Ramingstein
    Ramingstein is a small Austrian municipality in the Lungau region of Salzburg, known for its alpine setting and historic silver mining heritage.
  • 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_69da627278c88190babe4297a9df1236 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6632b2de48190abe2b277d89eb695 completed April 20, 2026, 5:32 p.m.
Created at: April 11, 2026, 3:37 p.m.