Triple

T26716722
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:CC E673585 entity
Predicate hasNoDefinedSubdivisions P195628 FINISHED
Object true 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: true | Statement: [ISO 3166-2:CC, hasNoDefinedSubdivisions, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNoDefinedSubdivisions
Context triple: [ISO 3166-2:CC, hasNoDefinedSubdivisions, true]
  • A. hasSubdivision
    Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
  • B. hasTerritorialSubdivisionType
    Indicates that an entity’s territorial subdivisions are of a specified administrative or geographic type (e.g., province, county, district).
  • C. hasNationalSubdivisionType
    Indicates that an entity is associated with a specific type or category of national-level administrative subdivision (e.g., state, province, region).
  • D. hasSubdivisionStandard
    Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
  • E. hasSubdivisionCode
    Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
  • 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_69eecda3a22881908f3061c760b9d542 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fddd373cdc8190be1b12e70e4deb1f completed May 8, 2026, 12:55 p.m.
PD Predicate disambiguation batch_69fddc6915a88190ad41e379aa3ede13 completed May 8, 2026, 12:51 p.m.
PDg Predicate description generation batch_69fddd364c1481908794c9d423bdc2d7 completed May 8, 2026, 12:55 p.m.
Created at: April 27, 2026, 3:38 a.m.