Triple
T23972773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê–Mạc War |
E604280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war in Vietnam |
C441
|
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: war in Vietnam Context triple: [Lê–Mạc War, instanceOf, war in Vietnam]
-
A.
event in the Vietnam War
An event in the Vietnam War is a specific, temporally bounded occurrence—such as a battle, operation, political decision, or diplomatic action—that significantly influenced the course, conduct, or consequences of the conflict.
-
B.
war in China
War in China encompasses the organized, large-scale armed conflicts that have occurred within or involving Chinese territory, states, or peoples, shaped by shifting dynasties, foreign invasions, civil strife, and modern geopolitical struggles.
-
C.
election in South Vietnam
An election in South Vietnam is a formal political process held in the former Republic of Vietnam to select government officials or decide public issues, typically under conditions shaped by wartime, foreign influence, and contested legitimacy.
-
D.
engagement of the Korean War
The engagement of the Korean War is a military operation or battle episode involving armed forces of opposing sides during the 1950–1953 conflict on the Korean Peninsula, characterized by direct combat, maneuver, and tactical interaction within a defined time and area.
-
E.
war
chosen
War is a large-scale, organized conflict between groups—typically nations or factions—characterized by sustained violence, strategic objectives, and significant political, social, and human consequences.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:25 p.m.