Triple

T9164276
Position Surface form Disambiguated ID Type / Status
Subject Weißenfels district E219906 entity
Predicate hadISO3166-2Code P42695 FINISHED
Object DE-ST — 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: DE-ST | Statement: [Weißenfels district, hadISO3166-2Code, DE-ST]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadISO3166-2Code
Context triple: [Weißenfels district, hadISO3166-2Code, DE-ST]
  • A. ISO3166-2RegionCode chosen
    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.
  • B. associatedSubdivisionISO3166-1Alpha2
    Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
  • C. hasISO3166-1NumericCode
    Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
  • D. parentISO3166Code
    Indicates that one geographic or political entity is hierarchically contained within or derived from another, as represented by its parent ISO 3166 country or region code.
  • 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_69ca83e3633c81908688a9fa2306ba99 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaa2ee64c8190a9a5abafe5d0b086 completed April 1, 2026, 5:16 a.m.
PD Predicate disambiguation batch_69cc6605c6808190a30d92da006206ac completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:21 p.m.