Triple

T29593158
Position Surface form Disambiguated ID Type / Status
Subject Bac Kan Province E754222 entity
Predicate hasEthnicLanguages P115409 FINISHED
Object Tay language NE NERFINISHED

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: Tay language | Statement: [Bac Kan Province, hasEthnicLanguages, Tay language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEthnicLanguages
Context triple: [Bac Kan Province, hasEthnicLanguages, Tay language]
  • A. hasEthnolinguisticPresence chosen
    Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
  • B. hasEthnolinguisticContext
    Indicates that something is associated with, shaped by, or understood within a specific ethnolinguistic (cultural and language-based) context.
  • C. areMinorityLanguagesIn
    Indicates that the subject languages are minority (non-dominant) languages within the specified region, country, or larger linguistic context.
  • D. hasIndigenousLanguageSpoken
    Indicates that an entity is associated with an indigenous language that is or was spoken by it or within its context.
  • E. hasEthnicScope
    Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic 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_69f0ef836ac88190bd809dc58b5ec907 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f6f8565134819096aac0175f924a9f completed May 3, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f6f65fd1d08190b88e5e68ba268500 completed May 3, 2026, 7:16 a.m.
Created at: April 28, 2026, 6:16 p.m.