Triple

T26629714
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:CL E668457 entity
Predicate hasSubdivisionCodeFor P22016 FINISHED
Object Región de Arica y Parinacota 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: Región de Arica y Parinacota | Statement: [ISO 3166-2:CL, hasSubdivisionCodeFor, Región de Arica y Parinacota]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSubdivisionCodeFor
Context triple: [ISO 3166-2:CL, hasSubdivisionCodeFor, Región de Arica y Parinacota]
  • A. hasSubdivisionCode chosen
    Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
  • B. hasSubdivisionCodePart
    Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
  • C. hasSubdivision
    Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
  • D. hasSubdivisionCodeContext
    Indicates that a subdivision code is interpreted within a specific coding or contextual framework that defines its meaning.
  • E. hasSubdivisionStandard
    Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
  • 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_69ee9cff507c819092b95bf7219a702e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
Created at: April 27, 2026, 2:24 a.m.