Triple
T3789135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiang Ying |
E89601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese Communist politician |
C4500
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Chinese Communist politician Context triple: [Xiang Ying, instanceOf, Chinese Communist politician]
-
A.
Republic of China politician
A Republic of China politician is a public official who participates in the governance and political processes of the Republic of China (Taiwan), typically through elected or appointed office at the national or local level.
-
B.
Chinese communist
chosen
A Chinese communist is an individual who supports or adheres to the principles, ideology, and political program of the Communist Party of China within the context of the Chinese socialist system.
-
C.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
D.
Yugoslav politician
A Yugoslav politician is a public official or political leader who operated within the federal structures, republics, or local governments of the former Socialist Federal Republic of Yugoslavia, shaping its domestic and foreign policies during its existence.
-
E.
East German politician
An East German politician is a public official or political figure who was active in the governance, administration, or party structures of the former German Democratic Republic (GDR) before its reunification with West Germany in 1990.
- F. None of above.
Provenance (1 batch)
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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.