Triple

T20051770
Position Surface form Disambiguated ID Type / Status
Subject Piotrków County E499216 entity
Predicate hasPostalCodeScheme P103944 FINISHED
Object Polish postal code system 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: Polish postal code system | Statement: [Piotrków County, hasPostalCodeScheme, Polish postal code system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPostalCodeScheme
Context triple: [Piotrków County, hasPostalCodeScheme, Polish postal code system]
  • A. hasPostalSystem
    Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
  • B. hasPostalCountryCode
    Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
  • C. hasPostalAddressSystem chosen
    Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
  • D. hasPostalFeature
    Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
  • E. hasPostalAuthority
    Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
  • F. None of above.

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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6632ee4d48190b9de3a1efa064492 completed April 20, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69e54cee7a5c819084ae4ff26419833f completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 3:38 p.m.