Triple

T18304086
Position Surface form Disambiguated ID Type / Status
Subject Ruiten Aa E438435 entity
Predicate hasAlternativeNameLanguageContext P63334 FINISHED
Object Gronings dialect names 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 names | Statement: [Ruiten Aa, hasAlternativeNameLanguageContext, Gronings dialect names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNameLanguageContext
Context triple: [Ruiten Aa, hasAlternativeNameLanguageContext, Gronings dialect names]
  • A. alternateLanguageName chosen
    Indicates that an entity has an additional name or label in a different language from its primary or default name.
  • B. hasAlternativeContext
    Indicates that something is associated with an additional or different contextual setting or interpretation beyond its primary one.
  • C. hasAlternativeFamilyName
    Indicates that an entity is associated with an additional or variant family name besides its primary family name.
  • D. hasAlternativeReferent
    Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
  • E. hasNameInLocalLanguage
    Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5018256508190b024980e3a4a3ae9 completed April 19, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.