Triple
T17297678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lu Hao-tung |
E419954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Tongmenghui |
C31551
|
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: member of Tongmenghui Context triple: [Lu Hao-tung, instanceOf, member of Tongmenghui]
-
A.
participant in the Xinhai Revolution
chosen
A participant in the Xinhai Revolution is an individual or organized group that actively contributed—politically, militarily, or logistically—to the 1911 uprising that overthrew the Qing dynasty and led to the establishment of the Republic of China.
-
B.
Beiyang clique member
A Beiyang clique member is an individual affiliated with the powerful military-political faction that emerged from Yuan Shikai’s Beiyang Army and dominated Chinese warlord politics in the early Republic of China.
-
C.
Zhili clique leader
A Zhili clique leader is a high-ranking military or political figure who commands and directs the factional interests, strategies, and operations of the Zhili clique within the broader context of early 20th-century Chinese warlord politics.
-
D.
founding member of Katipunan
A founding member of Katipunan is an individual who helped establish the secret revolutionary society in the Philippines in 1892, playing a key role in organizing and initiating its struggle for independence from Spanish colonial rule.
-
E.
member of the Zhu clan
A member of the Zhu clan is an individual belonging to a historically significant Chinese lineage, often associated with shared ancestry, cultural traditions, and familial identity under the Zhu surname.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:41 a.m.