Triple

T35380437
Position Surface form Disambiguated ID Type / Status
Subject Roßdorf E1022626 entity
Predicate hasEuropeanNUTSLevel2Region P145130 FINISHED
Object DE71 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: DE71 | Statement: [Roßdorf, hasEuropeanNUTSLevel2Region, DE71]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEuropeanNUTSLevel2Region
Context triple: [Roßdorf, hasEuropeanNUTSLevel2Region, DE71]
  • A. locatedInNUTS2 chosen
    Indicates that one entity is geographically situated within, or belongs to, a specific NUTS-2 (Nomenclature of Territorial Units for Statistics level 2) region.
  • B. NUTSRegionCode
    Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
  • C. belongsToEURegionType
    Indicates that an entity is classified within a specific type or category of European Union region.
  • D. hasSecondLevelAdministrativeTerritory
    Indicates that an entity possesses or includes a second-level administrative division within its territorial or organizational hierarchy.
  • E. includesBelgianRegion
    Indicates that one entity geographically or administratively contains or encompasses a region located in Belgium.
  • 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_69f76df28d8c819089f2c5799fe7d079 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f79da9f80c8190b0afd8509f28747b completed May 3, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69f79617d40481909ba372f94209c08b completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4:03 p.m.