Triple

T38544654
Position Surface form Disambiguated ID Type / Status
Subject DZ E924932 entity
Predicate correspondingUNCode P191751 FINISHED
Object 012 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: 012 | Statement: [DZ, correspondingUNCode, 012]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: correspondingUNCode
Context triple: [DZ, correspondingUNCode, 012]
  • A. hasUNCode
    Indicates that an entity is associated with a specific United Nations–assigned code that identifies it in UN systems or classifications.
  • B. recognizedByUNAsPartOf
    Indicates that an entity is officially acknowledged or accepted by the United Nations as belonging to, or constituting a component of, another specified entity or grouping.
  • C. ISOCode
    Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
  • D. designationByUNECE
    Indicates that an entity has been assigned an official designation or classification by the United Nations Economic Commission for Europe (UNECE).
  • E. UNLOCODE
    Indicates that an entity is associated with a specific UN/LOCODE, i.e., a standardized United Nations location code identifying a particular place used in international trade and transport.
  • 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_69f76eadeac081909cdfdd0474cb6765 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fce7671f108190bf3ebf54339068b5 completed May 7, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69fce5b5a84c81908ac1b5b9f08d48d0 completed May 7, 2026, 7:19 p.m.
PDg Predicate description generation batch_69fce76669408190b1beef8899a8a5e2 completed May 7, 2026, 7:26 p.m.
Created at: May 3, 2026, 4:32 p.m.