Triple

T12866239
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:ZA E307725 entity
Predicate subdivisionNameForCode P50511 FINISHED
Object ZA-EC = Eastern Cape 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: ZA-EC = Eastern Cape | Statement: [ISO 3166-2:ZA, subdivisionNameForCode, ZA-EC = Eastern Cape]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subdivisionNameForCode
Context triple: [ISO 3166-2:ZA, subdivisionNameForCode, ZA-EC = Eastern Cape]
  • A. subdivisionName0
    Indicates the name assigned to the first (primary) subdivision or sub-unit associated with an entity.
  • B. subdivisionNameLanguage
    Indicates the language in which the name of a subdivision (such as a region, district, or administrative unit) is expressed.
  • C. provincialSubdivisionName
    Indicates the name assigned to a first-level administrative or provincial subdivision within a larger territorial or political entity.
  • D. subdivisionISOName chosen
    Indicates the standardized ISO-recognized name assigned to a specific administrative subdivision within a country.
  • E. subdivisionName1
    Indicates that the first named subdivision is identified by a specific name or designation within a larger geographic or organizational hierarchy.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714208f881908f7f8a921362909a completed April 10, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69d96fa3002881908000357b1f95a3ac completed April 10, 2026, 9:46 p.m.
Created at: April 9, 2026, 5:38 p.m.