Triple

T8296411
Position Surface form Disambiguated ID Type / Status
Subject Degendorf E194229 entity
Predicate locatedIn P40 FINISHED
Object Lichtenfels E11679 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: Lichtenfels | Statement: [Degendorf, locatedIn, Lichtenfels]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lichtenfels
Context triple: [Degendorf, locatedIn, Lichtenfels]
  • A. Lichtenfels chosen
    Lichtenfels is a town in the Upper Franconia region of Bavaria, Germany, known for its basket-making tradition and historic architecture.
  • B. Lülsfeld
    Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • C. Markranstädt
    Markranstädt is a small town in the German state of Saxony, located near Leipzig and known for its local industry and proximity to the Kulkwitzer See recreation area.
  • D. Hildburghausen
    Hildburghausen is a town in the German state of Thuringia that historically served as the residence of the dukes of Saxe-Hildburghausen.
  • E. Lampoldshausen
    Lampoldshausen is a German village best known as a major site for rocket propulsion research and testing facilities of the German Aerospace Center.
  • 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_69ca82e50ebc81909aa7b260c76bd757 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7df887148190bddc2609bc885cb4 completed March 31, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf27abf324819098bd6ecfd5a4d8cc completed April 3, 2026, 2:36 a.m.
Created at: March 30, 2026, 5:53 p.m.