Triple

T3607608
Position Surface form Disambiguated ID Type / Status
Subject Hokkaido dialect of Japanese E76409 entity
Predicate containsRegionalVocabulary P49919 FINISHED
Object Hokkaido-specific lexical items 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: Hokkaido-specific lexical items | Statement: [Hokkaido dialect of Japanese, containsRegionalVocabulary, Hokkaido-specific lexical items]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsRegionalVocabulary
Context triple: [Hokkaido dialect of Japanese, containsRegionalVocabulary, Hokkaido-specific lexical items]
  • A. hasRegionalVariationsIn
    Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
  • B. recognizedRegionalLanguage
    Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
  • C. hasRegionalName
    Indicates that an entity is known by a specific name or designation within a particular region or locality.
  • D. regionalVariantOf
    Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
  • E. regionalDialect
    Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc228e24481909ae6a1e4ad796917 completed March 8, 2026, 6:38 p.m.
PD Predicate disambiguation batch_69adb83d8b1c8190b3bddbc5dc995a87 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb8e4ba948190a9b777cf7f788b96 completed March 8, 2026, 5:59 p.m.
Created at: March 8, 2026, 3:22 p.m.