Triple

T34837933
Position Surface form Disambiguated ID Type / Status
Subject ES52 E1004250 entity
Predicate ISO3166-2LinkedUnit P27650 FINISHED
Object ES-VC 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: ES-VC | Statement: [ES52, ISO3166-2LinkedUnit, ES-VC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ISO3166-2LinkedUnit
Context triple: [ES52, ISO3166-2LinkedUnit, ES-VC]
  • 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. ISO3166Relation
    Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
  • C. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • D. linkedToISO3166-2CodesOf chosen
    Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
  • E. countrySubdivisionStandardLink
    Indicates a reference or link to the standard or authoritative specification that defines the country’s internal subdivisions.
  • 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_69f76db97714819099b5bed36fd64e9d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f782f4f10081908f97f6d0d2dbeec7 completed May 3, 2026, 5:16 p.m.
PD Predicate disambiguation batch_69f780ff71cc8190a67e71076fbad81a completed May 3, 2026, 5:08 p.m.
Created at: May 3, 2026, 4 p.m.