Triple

T5284491
Position Surface form Disambiguated ID Type / Status
Subject Museum für Naturkunde Gera E119582 entity
Predicate locatedIn P40 FINISHED
Object Gera E22181 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: Gera | Statement: [Museum für Naturkunde Gera, locatedIn, Gera]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gera
Context triple: [Museum für Naturkunde Gera, locatedIn, Gera]
  • A. Gera
    Gera is a biblical figure mentioned in the Hebrew Bible, known primarily as a Benjamite ancestor in the genealogy of the tribe of Benjamin.
  • B. Gera chosen
    Gera is a city in the German state of Thuringia, known for its industrial heritage and historic architecture along the White Elster river.
  • C. Eschwege
    Eschwege is a small historic town in the German state of Hesse, known for its medieval architecture and location near the Werra River.
  • D. Morava
    Morava is a Central European river that forms part of the border between Austria, the Czech Republic, and Slovakia before joining the Danube near Bratislava.
  • E. Lahn
    The Lahn is a river in western Germany that flows through the states of North Rhine-Westphalia, Hesse, and Rhineland-Palatinate before joining the Rhine.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd84d693288190b437955e40ad6abb completed March 20, 2026, 5:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3a8c43988190814e3b2cca509f15 completed March 22, 2026, 12:40 a.m.
Created at: March 20, 2026, 1:52 p.m.