Triple

T12033805
Position Surface form Disambiguated ID Type / Status
Subject Frechen E286481 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Pulheim E598842 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: Pulheim | Statement: [Frechen, hasNeighbouringMunicipality, Pulheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pulheim
Context triple: [Frechen, hasNeighbouringMunicipality, Pulheim]
  • A. Pulheim chosen
    Pulheim is a town in western Germany’s North Rhine-Westphalia, situated just northwest of Cologne within the broader Cologne/Bonn urban area.
  • B. Puchheim
    Puchheim is a small town in Upper Bavaria, Germany, situated near Munich and known as a residential and commuter community.
  • C. Fluntern
    Fluntern is a residential district in the city of Zurich, Switzerland, known for its hillside location, green spaces, and cultural landmarks.
  • D. Meerbusch
    Meerbusch is a town in the German state of North Rhine-Westphalia, situated on the west bank of the Rhine near Düsseldorf and known for its affluent residential areas and green surroundings.
  • E. Sulzheim
    Sulzheim is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040724ec8190808f334013ddc6d6 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6af3b91288190ab2df6103bfa5a91 completed May 3, 2026, 2:13 a.m.
Created at: April 8, 2026, 9:47 p.m.