Triple

T28427789
Position Surface form Disambiguated ID Type / Status
Subject Municipality of Kočevje E715035 entity
Predicate formerLanguageCommunity P195347 FINISHED
Object Gottscheerish 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: Gottscheerish | Statement: [Municipality of Kočevje, formerLanguageCommunity, Gottscheerish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerLanguageCommunity
Context triple: [Municipality of Kočevje, formerLanguageCommunity, Gottscheerish]
  • A. hasLanguageCommunity
    Indicates that an entity is associated with or serves a particular language community.
  • B. formerLanguage
    Indicates that one entity was previously the language of another entity but is no longer in that role.
  • C. oneOfLastCommunitiesWhereLanguageSpoken
    Indicates that the subject community is among the final remaining communities in which the specified language is still actively spoken.
  • D. formerLanguageRegion
    Indicates that a region previously used a particular language as significant or dominant, but no longer does so.
  • E. hasNeighboringLanguageCommunity
    Indicates that one language community is geographically or socially adjacent to another, allowing for direct contact or interaction between them.
  • 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_69efd6b253888190b3c7222ed6a403a8 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69fdbc5ef46c8190bbcfb9798f4615b7 completed May 8, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69fdbb270338819082ce3f73903e884f completed May 8, 2026, 10:29 a.m.
PDg Predicate description generation batch_69fdbc5da9988190b95234bce4cc2062 completed May 8, 2026, 10:35 a.m.
Created at: April 28, 2026, 1:38 a.m.