Triple

T9675117
Position Surface form Disambiguated ID Type / Status
Subject National Revolutionary Army E234127 entity
Predicate commander P1061 FINISHED
Object Xue Yue E29744 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: Xue Yue | Statement: [National Revolutionary Army, commander, Xue Yue]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Xue Yue
Context triple: [National Revolutionary Army, commander, Xue Yue]
  • A. Xue Yue chosen
    Xue Yue was a prominent Nationalist Chinese general renowned for his leadership in key battles against Japanese forces during the Second Sino-Japanese War.
  • B. Xue Jianyue
    Xue Jianyue is a person notable for bearing the Chinese surname Xue.
  • C. Yuan Xinyue
    Yuan Xinyue is a Chinese professional volleyball player known for her height, middle-blocker role, and key contributions to China’s national team in major international competitions.
  • D. Xue Yuyang
    Xue Yuyang is a relatively obscure individual bearing the Chinese surname Xue, with limited publicly available biographical or professional information.
  • E. Xue Xiaoqing
    Xue Xiaoqing is a notable individual who bears the Chinese surname Xue, recognized as a distinguished representative of that family name.
  • 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c6d6dd48190a77c486337a58cb6 completed April 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69d190f9bf78819093542adae997a668 completed April 4, 2026, 10:30 p.m.
Created at: March 30, 2026, 8:15 p.m.