Triple

T27542039
Position Surface form Disambiguated ID Type / Status
Subject 客家话 E695260 entity
Predicate 代表方言点 P152424 FINISHED
Object 广东五华话 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: 广东五华话 | Statement: [客家话, 代表方言点, 广东五华话]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 代表方言点
Context triple: [客家话, 代表方言点, 广东五华话]
  • A. regionalDialect
    Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
  • B. hasDialectContinuumWith
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • C. denotesLanguageVariety chosen
    Indicates that one entity specifies the particular variety, dialect, or form of language used or associated with another entity.
  • D. hasDialectalDifferenceWith
    Indicates that two language varieties differ from each other in dialectal features such as pronunciation, vocabulary, or grammar.
  • E. regionOfDialectContinuum
    Indicates that a dialect continuum is associated with, or occurs within, a specific geographic 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_69ef5386c3e08190bfe33aa326e1f72b completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62f5ec8b481909241271f7d602dc9 completed May 2, 2026, 5:07 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 1:31 p.m.