Triple

T7486780
Position Surface form Disambiguated ID Type / Status
Subject CL-CO E176900 entity
Predicate partOf P40 FINISHED
Object ISO 3166-2:CL
ISO 3166-2:CL is the section of the ISO 3166-2 standard that defines the official subdivision codes for the regions of Chile.
 E668457 NE FINISHED

How this triple was built (4 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: ISO 3166-2:CL | Statement: [CL-CO, partOf, ISO 3166-2:CL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ISO 3166-2:CL
Context triple: [CL-CO, partOf, ISO 3166-2:CL]
  • A. ISO 3166-2:SM
    ISO 3166-2:SM is the subdivision code set within the ISO 3166-2 standard that defines codes for the principal subdivisions of San Marino.
  • B. ISO 3166-2:AD
    ISO 3166-2:AD is the ISO 3166-2 entry that defines the principal subdivision codes for the country of Andorra.
  • C. ISO 3166-2:ST
    ISO 3166-2:ST is the ISO 3166-2 entry that defines the principal subdivision codes for São Tomé and Príncipe.
  • D. ISO 3166-2:GB
    ISO 3166-2:GB is the part of the ISO 3166-2 standard that defines the official codes for the principal subdivisions (such as countries of the UK and their administrative areas) of the United Kingdom.
  • E. ISO 3166-2:LI
    ISO 3166-2:LI is the ISO 3166-2 subdivision code entry that defines the principal subdivisions of Liechtenstein for use in international standards and data exchange.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ISO 3166-2:CL
Triple: [CL-CO, partOf, ISO 3166-2:CL]
Generated description
ISO 3166-2:CL is the section of the ISO 3166-2 standard that defines the official subdivision codes for the regions of Chile.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: ISO 3166-2:CL
Target entity description: ISO 3166-2:CL is the section of the ISO 3166-2 standard that defines the official subdivision codes for the regions of Chile.
  • A. ISO 3166-2:SM
    ISO 3166-2:SM is the subdivision code set within the ISO 3166-2 standard that defines codes for the principal subdivisions of San Marino.
  • B. ISO 3166-2:AD
    ISO 3166-2:AD is the ISO 3166-2 entry that defines the principal subdivision codes for the country of Andorra.
  • C. ISO 3166-2:ST
    ISO 3166-2:ST is the ISO 3166-2 entry that defines the principal subdivision codes for São Tomé and Príncipe.
  • D. ISO 3166-2:GB
    ISO 3166-2:GB is the part of the ISO 3166-2 standard that defines the official codes for the principal subdivisions (such as countries of the UK and their administrative areas) of the United Kingdom.
  • E. ISO 3166-2:LI
    ISO 3166-2:LI is the ISO 3166-2 subdivision code entry that defines the principal subdivisions of Liechtenstein for use in international standards and data exchange.
  • F. None of above. chosen

Provenance (5 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_69c69f24ac508190bb98fe927c0bd065 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f5582adc81908b68439762965d88 completed March 27, 2026, 9:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83c68bcf081908a2c280152d887f0 completed March 28, 2026, 8:39 p.m.
NEDg Description generation batch_69c83ddda5688190be1ec69f23671f60 completed March 28, 2026, 8:45 p.m.
NED2 Entity disambiguation (via description) batch_69c83e42b0048190b1abd8ae99c97e38 completed March 28, 2026, 8:46 p.m.
Created at: March 27, 2026, 3:42 p.m.