Triple
T4293568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangzhou Uprising |
E99653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary event in China |
C15541
|
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: revolutionary event in China Context triple: [Guangzhou Uprising, instanceOf, revolutionary event in China]
-
A.
revolutionary event in Germany
A revolutionary event in Germany is a significant, often abrupt socio-political upheaval within German territory that challenges or overturns existing power structures, institutions, or social orders.
-
B.
phase of the Chinese Civil War
A phase of the Chinese Civil War is a distinct, time-bounded period characterized by specific patterns of military conflict, political strategies, territorial control, and key events between the major opposing forces.
-
C.
phase of the Chinese Civil War
A phase of the Chinese Civil War is a distinct period characterized by specific political, military, and social dynamics that collectively define a recognizable stage in the broader conflict between the Chinese Communist Party and the Kuomintang.
-
D.
event in the Russian Revolution
An event in the Russian Revolution is a significant historical occurrence—such as a protest, decree, battle, or political change—that contributed to the overthrow of the tsarist regime and the subsequent rise of Soviet power.
-
E.
anti-Chinese incident
An anti-Chinese incident is an event or action, ranging from verbal harassment to physical violence or discriminatory policies, specifically targeting individuals, communities, or institutions perceived as Chinese.
- F. None of above. chosen
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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.