Triple

T5076678
Position Surface form Disambiguated ID Type / Status
Subject He Yingqin E114413 entity
Predicate givenName P17 FINISHED
Object Yingqin E114413 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: Yingqin | Statement: [He Yingqin, givenName, Yingqin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yingqin
Context triple: [He Yingqin, givenName, Yingqin]
  • A. Yingqin chosen
    Yingqin is the given name of He Yingqin, a prominent Chinese Nationalist military leader and politician of the early 20th century.
  • B. Qinghe
    Qinghe is a subdistrict in Beijing’s Haidian District, known primarily as a residential and administrative area within the city’s northwestern urban zone.
  • C. Heqing
    Heqing was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
  • D. Yingtian
    Yingtian was an important early Ming dynasty capital city, historically centered around present-day Nanjing in China.
  • E. Qiying
    Qiying was a Qing dynasty statesman and diplomat who played a key role in negotiating several unequal treaties with Western powers in the mid-19th century.
  • 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_69bd443dbf908190a9401e9c2dc7bd7d completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd74d3b0088190a658864cb120eef4 completed March 20, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69beb121fa388190ab3909d20f014b6f completed March 21, 2026, 2:54 p.m.
Created at: March 20, 2026, 1:39 p.m.