Triple

T5051376
Position Surface form Disambiguated ID Type / Status
Subject St. Michaelis-Kirche (Fürth) E113792 entity
Predicate locatedIn P40 FINISHED
Object Fürth E44190 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: Fürth | Statement: [St. Michaelis-Kirche (Fürth), locatedIn, Fürth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fürth
Context triple: [St. Michaelis-Kirche (Fürth), locatedIn, Fürth]
  • A. Fürth chosen
    Fürth is a historic city in northern Bavaria, Germany, known for its well-preserved old town and proximity to Nuremberg within the Franconian metropolitan region.
  • B. Freyung
    Freyung is a small town in southeastern Bavaria, Germany, known as a gateway to the Bavarian Forest region.
  • C. Idstein
    Idstein is a historic town in the German state of Hesse, known for its well-preserved medieval old town and timber-framed architecture.
  • D. Hallein
    Hallein is a historic town in the Austrian state of Salzburg, known for its former salt mines and picturesque location along the Salzach River.
  • E. Starnberg
    Starnberg is a lakeside town in Bavaria, Germany, known for its affluent residential character and scenic location on Lake Starnberg southwest of Munich.
  • 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_69bd443aa1f88190abb992d138f2cf42 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7426fc8081908a8227f73168c235 completed March 20, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea483b6cc8190b3b48598a291d708 completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:37 p.m.