Triple

T37015720
Position Surface form Disambiguated ID Type / Status
Subject Ticino E916073 entity
Predicate ISO_3166_2 P42695 FINISHED
Object CH-TI 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: CH-TI | Statement: [Ticino, ISO_3166_2, CH-TI]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ISO_3166_2
Context triple: [Ticino, ISO_3166_2, CH-TI]
  • A. ISO3166-2RegionCode chosen
    Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
  • B. associatedSubdivisionISO3166-1Alpha2
    Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
  • 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. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • E. ISO3166Relation
    Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
  • 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_69f76e920dc48190acb6bb7ebc4dffab completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb154c0fe08190a2e41e7a29b6055f completed May 6, 2026, 10:17 a.m.
PD Predicate disambiguation batch_69f9fecc005c8190be082a8689193745 completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:14 p.m.