Triple

T10755211
Position Surface form Disambiguated ID Type / Status
Subject .wf E253672 entity
Predicate iso3166Basis P42017 FINISHED
Object ISO 3166-1 alpha-2 code WF 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: ISO 3166-1 alpha-2 code WF | Statement: [.wf, iso3166Basis, ISO 3166-1 alpha-2 code WF]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: iso3166Basis
Context triple: [.wf, iso3166Basis, ISO 3166-1 alpha-2 code WF]
  • A. ISO3166Basis chosen
    Indicates that one standard, classification, or designation is defined or derived based on the ISO 3166 country code system.
  • B. iso3166CodeBasedOn
    Indicates that one code or designation is derived from, corresponds to, or is assigned on the basis of a specific ISO 3166 country or region code.
  • C. ISO3166Status
    Indicates the classification or current standing of an entity under the ISO 3166 country code standard (e.g., official, reserved, or deleted status).
  • D. ISO3166Relation
    Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
  • E. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d72e9d0f688190a9be024929d2f960 completed April 9, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69d6f311529c819080ca5493d55d6050 completed April 9, 2026, 12:30 a.m.
Created at: April 8, 2026, 9:15 p.m.