Triple

T29689164
Position Surface form Disambiguated ID Type / Status
Subject Foong E751167 entity
Predicate derivedFromLanguageVariety P64609 FINISHED
Object Southern Chinese dialects 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: Southern Chinese dialects | Statement: [Foong, derivedFromLanguageVariety, Southern Chinese dialects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: derivedFromLanguageVariety
Context triple: [Foong, derivedFromLanguageVariety, Southern Chinese dialects]
  • A. partOfLinguisticVariety chosen
    Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
  • B. denotesLanguageVariety
    Indicates that one entity specifies the particular variety, dialect, or form of language used or associated with another entity.
  • C. derivedFromLanguageFamily
    Indicates that one language originates from, or historically descends from, a particular language family.
  • D. hasLinguisticVariety
    Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
  • E. primaryLanguageVariety
    Indicates the main dialect or specific variety of a language that an entity primarily uses.
  • 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_69f0d625b09481909b0b69aea1e846c8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6953bafb88190a860e9c68a3dd4b2 completed May 3, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69f690ed5d008190831cf8e44cce28af completed May 3, 2026, 12:03 a.m.
Created at: April 28, 2026, 7:15 p.m.