Triple

T28547568
Position Surface form Disambiguated ID Type / Status
Subject Huizhou Hakka E722487 entity
Predicate dialectContinuum P18451 FINISHED
Object Hakka dialect continuum 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: Hakka dialect continuum | Statement: [Huizhou Hakka, dialectContinuum, Hakka dialect continuum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dialectContinuum
Context triple: [Huizhou Hakka, dialectContinuum, Hakka dialect continuum]
  • A. hasDialectContinuumWith chosen
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • B. regionOfDialectContinuum
    Indicates that a dialect continuum is associated with, or occurs within, a specific geographic region.
  • C. usedInDialectContinuum
    Indicates that something (such as a linguistic feature or form) is employed within and across varieties in a dialect continuum, rather than being confined to a single discrete dialect.
  • D. containsDialectContinuum
    Indicates that one linguistic variety or region includes within it a dialect continuum, where neighboring dialects are mutually intelligible but differences accumulate over distance.
  • E. dialectDocumentation
    Indicates that there exists documentation or descriptive information specifically about a particular dialect or dialectal variety.
  • 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_69f01a5e42348190b1ffbca26e739c84 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f652a492108190b885b955ce147d3c completed May 2, 2026, 7:38 p.m.
PD Predicate disambiguation batch_69f651aad92c8190b874b3b5f9f64434 completed May 2, 2026, 7:34 p.m.
Created at: April 28, 2026, 3:40 a.m.