Triple
T18859663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhou Baozhong |
E461275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Japanese resistance fighter |
C4781
|
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: anti-Japanese resistance fighter Context triple: [Zhou Baozhong, instanceOf, anti-Japanese resistance fighter]
-
A.
resistance fighter
chosen
A resistance fighter is an individual who actively opposes and combats an occupying force, oppressive regime, or unjust authority, often through clandestine, guerrilla, or subversive means.
-
B.
Korean independence activist
A Korean independence activist is an individual who actively resists foreign rule and advocates for Korea’s political sovereignty, cultural preservation, and national self-determination.
-
C.
World War II resistance member
A World War II resistance member is an individual who clandestinely opposed Axis occupation or authoritarian regimes through activities such as sabotage, intelligence gathering, underground communication, and support for persecuted populations.
-
D.
guerrilla leader
A guerrilla leader is a commander who organizes, directs, and motivates small, irregular combat groups to conduct unconventional warfare, often using hit-and-run tactics and local support against a typically stronger adversary.
-
E.
Indonesian revolutionary
An Indonesian revolutionary is an individual who actively participates in or leads efforts to challenge and transform Indonesia’s political, social, or colonial structures, particularly during the struggle for independence and subsequent nation-building.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.