Triple

T21205849
Position Surface form Disambiguated ID Type / Status
Subject Ankum E522576 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Kettenkamp 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: Kettenkamp | Statement: [Ankum, hasNeighbouringMunicipality, Kettenkamp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kettenkamp
Context triple: [Ankum, hasNeighbouringMunicipality, Kettenkamp]
  • A. Kettenkamp chosen
    Kettenkamp is a small municipality in Lower Saxony, Germany, situated in the rural Osnabrück region.
  • B. Kettenis
    Kettenis is a village and municipal section of the city of Eupen in the German-speaking Community of eastern Belgium.
  • C. Steinkamp
    Steinkamp is a surname most notably associated with American film editor Fredric Steinkamp.
  • D. Kette
    Kette was a basic tactical unit of the German Luftwaffe in World War II, typically consisting of a small formation of aircraft flying and fighting together.
  • E. Kampen
    Kampen is a historic residential neighborhood in Oslo, Norway, known for its wooden houses, hillside location, and views over the city.
  • 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734342e9081909e241bed54dbc0b4 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:20 p.m.