Triple

T17949711
Position Surface form Disambiguated ID Type / Status
Subject Liu Bocheng E448800 entity
Predicate givenName P17 FINISHED
Object Bocheng 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: Bocheng | Statement: [Liu Bocheng, givenName, Bocheng]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bocheng
Context triple: [Liu Bocheng, givenName, Bocheng]
  • A. Bocheng chosen
    Bocheng is a Chinese given name most notably borne by the prominent Communist military leader and strategist Liu Bocheng.
  • B. Beipiao
    Beipiao is a county-level city in western Liaoning Province, China, known for its rich fossil deposits and significant paleontological discoveries.
  • C. Yifang
    Yifang is a given name of Chinese origin used for both males and females.
  • D. Dunhua
    Dunhua is a county-level city in northeastern China's Jilin Province, known for its location within the Yanbian Korean Autonomous Prefecture and its mix of Han and Korean cultural influences.
  • E. Shancheng
    Shancheng is a Chinese nickname meaning "Mountain City," commonly used to refer to the city of Chongqing, known for its steep terrain and hilly urban landscape.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afab8d988190b6c06d7406fb64c1 completed April 19, 2026, 10:34 a.m.
Created at: April 10, 2026, 10:21 a.m.