Triple

T38180943
Position Surface form Disambiguated ID Type / Status
Subject Rottum E1005158 entity
Predicate hasSecondaryLocalLanguage P9103 FINISHED
Object Gronings dialect 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: Gronings dialect | Statement: [Rottum, hasSecondaryLocalLanguage, Gronings dialect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondaryLocalLanguage
Context triple: [Rottum, hasSecondaryLocalLanguage, Gronings dialect]
  • A. hasSecondaryLanguage chosen
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • B. hasSecondaryNationalLanguage
    Indicates that an entity possesses an officially recognized secondary national language in addition to its primary national language.
  • C. hasSecondaryLanguageFamily
    Indicates that an entity has an additional, non-primary association with a particular language family.
  • D. hasSecondaryLanguageNearby
    Indicates that an entity has at least one secondary language present or used in its immediate vicinity or surrounding context.
  • E. laterSecondaryLanguageOfAdministration
    Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
  • 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_69f76dbc22c481908139b694ffde7a0c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a00bf5990e08190a8b633e237656564 completed May 10, 2026, 5:24 p.m.
PD Predicate disambiguation batch_6a00beef4f5881909b00ac89e6af5902 completed May 10, 2026, 5:22 p.m.
Created at: May 3, 2026, 4:29 p.m.