Triple

T35395497
Position Surface form Disambiguated ID Type / Status
Subject Eastern Thuringia E1023061 entity
Predicate historicalRegionAround P202718 FINISHED
Object Gera NE NERFINISHED

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: Gera | Statement: [Eastern Thuringia, historicalRegionAround, Gera]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRegionAround
Context triple: [Eastern Thuringia, historicalRegionAround, Gera]
  • A. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • B. historicalFocusRegion
    Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
  • C. historicalRegionOfInfluence
    Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
  • D. historicallyImportantRegion
    Indicates that a region holds significant importance due to its impact on historical events, developments, or cultural heritage.
  • E. historicalRegionCorrespondsTo
    Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
  • 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_69f76df34ba48190bd80f0814cdcd540 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a00af6b3a948190a92813c13384c304 completed May 10, 2026, 4:16 p.m.
PD Predicate disambiguation batch_6a00aec35610819085dd5137715a4228 completed May 10, 2026, 4:13 p.m.
PDg Predicate description generation batch_6a00af6a5ffc819095c7331518a09f53 completed May 10, 2026, 4:16 p.m.
Created at: May 3, 2026, 4:03 p.m.