Triple
T7385110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Nationalist side in the Second Sino-Japanese War |
E170360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political–military coalition |
C458
|
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: political–military coalition Context triple: [Chinese Nationalist side in the Second Sino-Japanese War, instanceOf, political–military coalition]
-
A.
coalition
chosen
A coalition is a temporary or long-term alliance of individuals, groups, or organizations that coordinate their resources and actions to achieve shared goals or exert collective influence.
-
B.
religious and political alliance
A religious and political alliance is a coalition in which faith-based groups and political actors formally or informally coordinate their agendas, resources, and influence to pursue shared ideological, social, or policy goals.
-
C.
political union
A political union is a formal association of two or more political entities that share or merge governance structures to coordinate policies, laws, and collective decision-making.
-
D.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
E.
multinational military forum
A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:08 p.m.