Triple

T963667
Position Surface form Disambiguated ID Type / Status
Subject Büsingen am Hochrhein E20788 entity
Predicate alsoServedByPostalCodeSystem P21911 FINISHED
Object Swiss postal codes of surrounding area LITERAL 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: Swiss postal codes of surrounding area | Statement: [Büsingen am Hochrhein, alsoServedByPostalCodeSystem, Swiss postal codes of surrounding area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alsoServedByPostalCodeSystem
Context triple: [Büsingen am Hochrhein, alsoServedByPostalCodeSystem, Swiss postal codes of surrounding area]
  • A. postalCodeSystem
    Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
  • B. hasPostalSystem
    Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
  • C. postalArea
    Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
  • D. hasPostalCodePrefix
    Indicates that a location’s postal code begins with a specified sequence of characters.
  • E. hasPostalRole
    Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
  • F. None of above. chosen

Provenance (4 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_69a493b21f2881908132dcf45dcd2f36 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b416cf4c8190bd685227db25fb53 completed March 1, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69a4b2a2e23c8190b932fe88b02f995d completed March 1, 2026, 9:41 p.m.
PDg Predicate description generation batch_69a4b326d9d88190913c1a892a795707 completed March 1, 2026, 9:44 p.m.
Created at: March 1, 2026, 7:40 p.m.