Triple

T7015680
Position Surface form Disambiguated ID Type / Status
Subject WB E162693 entity
Predicate ISO3166Relation P75262 FINISHED
Object not an ISO 3166 code 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: not an ISO 3166 code | Statement: [WB, ISO3166Relation, not an ISO 3166 code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ISO3166Relation
Context triple: [WB, ISO3166Relation, not an ISO 3166 code]
  • A. ISO3166Basis
    Indicates that one standard, classification, or designation is defined or derived based on the ISO 3166 country code system.
  • B. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • C. linkedToISO3166-2CodesOf
    Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
  • D. 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.
  • E. ISO3166-1Code
    Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
  • 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_69c6885a127c8190867b059bdccf13ff completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e5ecd4488190bf19e42de55da98b completed March 27, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69c6e1b8118481909d76eb6616160e80 completed March 27, 2026, 7:59 p.m.
PDg Predicate description generation batch_69c6e5eb904481909a900e2ba9df710b completed March 27, 2026, 8:17 p.m.
Created at: March 27, 2026, 2:34 p.m.