Triple

T9046703
Position Surface form Disambiguated ID Type / Status
Subject Hu Shi E216772 entity
Predicate givenName P17 FINISHED
Object Shi E85662 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: Shi | Statement: [Hu Shi, givenName, Shi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shi
Context triple: [Hu Shi, givenName, Shi]
  • A. Shi chosen
    Shi is a Chinese surname historically associated with members of the Jewish community in Kaifeng, China.
  • B. Shi
    The Shi are a Bantu-speaking ethnic group primarily inhabiting the South Kivu region of the eastern Democratic Republic of the Congo, known for their agrarian lifestyle and rich cultural traditions.
  • C. Shen
    Shen is a Chinese surname historically borne by notable figures such as the Song dynasty polymath Shen Kuo.
  • D. Shengzhi
    Shengzhi is the given name of Tang Shengzhi, a prominent Chinese Nationalist general active during the early 20th century.
  • E. Jian
    Jian is the given name of Ma Jian, a prominent Chinese-born writer known for his politically charged fiction and essays critical of contemporary China.
  • 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_69ca83d22d488190adbce5e020e9cd1d completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6b4e4b888190a425e29b193b506f completed April 1, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfebb7f668819099125ab727cd50b1 completed April 3, 2026, 4:32 p.m.
Created at: March 30, 2026, 7:09 p.m.