Triple

T23028166
Position Surface form Disambiguated ID Type / Status
Subject Lannesdorf E573380 entity
Predicate hasNeighbouringDistrict P17964 FINISHED
Object Mehlem 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: Mehlem | Statement: [Lannesdorf, hasNeighbouringDistrict, Mehlem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mehlem
Context triple: [Lannesdorf, hasNeighbouringDistrict, Mehlem]
  • A. Mehlem chosen
    Mehlem is a subdistrict of the Bonn borough of Bad Godesberg in Germany, known for its scenic location along the Rhine River.
  • B. Muhr
    Muhr is a small Austrian municipality located in the mountainous Lungau region of the state of Salzburg.
  • C. Melenki
    Melenki is a small town in western Russia known for its traditional provincial character within the historical region of central European Russia.
  • D. Mehli
    Mehli is the given name of Mehli Mehta, an Indian conductor and violinist known for his contributions to Western classical music and for being the father of conductor Zubin Mehta.
  • E. Mellte
    Mellte is a river in South Wales known for its scenic gorges, waterfalls, and popularity with walkers and canyoners.
  • 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847f453881909a8f2affb48c64f1 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.