Triple

T847072
Position Surface form Disambiguated ID Type / Status
Subject Shenzhen E18299 entity
Predicate language P15 FINISHED
Object Hakka E34449 NE 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 | Statement: [Shenzhen, language, Hakka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hakka
Context triple: [Shenzhen, language, Hakka]
  • A. Hakka chosen
    Hakka is a Sinitic language spoken primarily by the Hakka people across southern China and various overseas Chinese communities.
  • B. Guanggu
    Guanggu is a major high-tech development zone in Wuhan, China, known as an innovation hub for the optics and electronics industries.
  • C. Paihuano
    Paihuano is a small town and commune in Chile’s Elqui Valley, known for its clear skies, pisco production, and astrotourism.
  • D. Shina
    Shina is an Indo-Aryan language spoken primarily in the Gilgit-Baltistan region of Pakistan and surrounding Himalayan areas.
  • E. Kitchawan
    Kitchawan is a small hamlet within the town of Yorktown in Westchester County, New York, known for its residential character and proximity to natural areas.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac0ba6b4819089c15ed7e1765502 completed March 1, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7a3bd8b588190b7a9eb72dce93d07 completed March 4, 2026, 3:15 a.m.
Created at: March 1, 2026, 7:38 p.m.