Triple

T11279785
Position Surface form Disambiguated ID Type / Status
Subject Rhein-Sieg-Kreis E267032 entity
Predicate contains P35 FINISHED
Object Lohmar E688098 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: Lohmar | Statement: [Rhein-Sieg-Kreis, contains, Lohmar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lohmar
Context triple: [Rhein-Sieg-Kreis, contains, Lohmar]
  • A. Lohmar chosen
    Lohmar is a town in the Rhein-Sieg district of North Rhine-Westphalia, Germany, situated near Cologne and known for its green surroundings and residential character.
  • B. Andernach
    Andernach is a historic German town on the Rhine River in Rhineland-Palatinate, known for its medieval architecture and one of the world’s highest cold-water geysers.
  • C. Gummersbach
    Gummersbach is a town in North Rhine-Westphalia, Germany, known as a regional center in the Bergisches Land and a location for higher education and industry.
  • D. Fritzlar
    Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
  • E. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e969b3448190940e2bd499d2d7de completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69f01869e6c8819093f2768b57b183aa completed April 28, 2026, 2:16 a.m.
Created at: April 8, 2026, 9:31 p.m.