Triple

T12816795
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Ennepetal E306422 entity
Predicate hasPrimaryLanguageType P98127 FINISHED
Object vernacular 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: vernacular | Statement: [Bishopric of Ennepetal, hasPrimaryLanguageType, vernacular]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLanguageType
Context triple: [Bishopric of Ennepetal, hasPrimaryLanguageType, vernacular]
  • A. hasPrimaryLanguage1
    Indicates that an entity’s main or most commonly used language is the specified language.
  • B. hasLanguageType
    Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
  • C. hasPrimaryLanguageBranch
    Indicates that an entity’s main or dominant language belongs to a specified language branch or family.
  • D. primaryLanguageType chosen
    Indicates the main category or kind of language (such as spoken, written, or signed) that serves as the primary mode of communication in a given context or for a given entity.
  • E. hasPrimaryLanguageSubbranch
    Indicates that one language subbranch is the main or principal subbranch associated with a given language or language family.
  • 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_69d7bdf46c448190b1faa55aaacb6317 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e9d00088190ac0f5d60e1de7a7c completed April 10, 2026, 9:41 p.m.
PD Predicate disambiguation batch_69d9640ed7448190b276e7fab649f7d2 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:31 p.m.