Triple

T30747704
Position Surface form Disambiguated ID Type / Status
Subject CZ071 E782858 entity
Predicate hasNUTS1ParentCode P52934 FINISHED
Object CZ0 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: CZ0 | Statement: [CZ071, hasNUTS1ParentCode, CZ0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNUTS1ParentCode
Context triple: [CZ071, hasNUTS1ParentCode, CZ0]
  • A. formerNUTSCode
    Indicates that an entity was previously identified by a specific NUTS (Nomenclature of Territorial Units for Statistics) regional code that is no longer current.
  • B. previousNUTSVersion
    Indicates that one NUTS (Nomenclature of Territorial Units for Statistics) classification version directly precedes another in the version sequence.
  • C. NUTSRegionCode
    Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
  • D. hasParentSubdivisionSet
    Indicates that an entity is associated with a set of higher-level subdivisions to which it belongs or from which it is derived.
  • E. hasHigherLevelRegion chosen
    Indicates that one region is geographically or administratively contained within and subordinate to a larger, higher-level region.
  • 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_69f224af8d8481908bea03890c5618be completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd68abf52881909c5a390c362b7c59 completed May 8, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69fd6812d0c88190930d8fa2d4b92490 completed May 8, 2026, 4:35 a.m.
Created at: April 29, 2026, 8:38 p.m.