Triple

T21419714
Position Surface form Disambiguated ID Type / Status
Subject SK E528402 entity
Predicate hasISO3166-2CodePrefix P143895 FINISHED
Object SK- 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: SK- | Statement: [SK, hasISO3166-2CodePrefix, SK-]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasISO3166-2CodePrefix
Context triple: [SK, hasISO3166-2CodePrefix, SK-]
  • A. ISO3166-2RegionCode
    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. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • C. 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.
  • D. ISO3166codePredecessorOf
    Indicates that one ISO 3166 country code served as the predecessor or was replaced by another ISO 3166 country code in the standard’s historical sequence.
  • E. associatedCountrySubdivisionCode
    Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
  • 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b2ccddc08190b4f66fa6ccda41e2 completed April 22, 2026, 11:36 a.m.
PD Predicate disambiguation batch_69e61633f8208190a2a849457c4e4198 completed April 20, 2026, 12:04 p.m.
PDg Predicate description generation batch_69e6190163448190a2404b396215c686 completed April 20, 2026, 12:16 p.m.
Created at: April 16, 2026, 5:47 p.m.