Triple

T17508889
Position Surface form Disambiguated ID Type / Status
Subject Hui’an County E426396 entity
Predicate hasLocalVariantOfDialect P84576 FINISHED
Object Hui’an 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: Hui’an dialect | Statement: [Hui’an County, hasLocalVariantOfDialect, Hui’an dialect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalVariantOfDialect
Context triple: [Hui’an County, hasLocalVariantOfDialect, Hui’an dialect]
  • A. hasNumberOfDialects
    Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
  • B. usesLocalLanguageVariant
    Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
  • C. hasLinguisticVariety chosen
    Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
  • D. isDialectalBaseOf
    Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
  • E. hasDialectsIn
    Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
  • 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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4525a43208190b8728214767428c0 completed April 19, 2026, 3:56 a.m.
PD Predicate disambiguation batch_69e3b4f5fbcc8190a6ea9639bf5650da completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:48 a.m.