Triple
T5299210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanker War |
E119933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military conflict phase |
C180
|
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: military conflict phase Context triple: [Tanker War, instanceOf, military conflict phase]
-
A.
military campaign phase
chosen
A military campaign phase is a distinct, time-bounded segment of a broader military operation characterized by specific objectives, actions, and resource allocations that contribute to the overall strategic goal.
-
B.
military confrontation
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
C.
guerrilla conflict
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
D.
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.
-
E.
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.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:53 p.m.