Triple
T7024599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linebacker I |
E162911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vietnam War operation |
C886
|
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: Vietnam War operation Context triple: [Linebacker I, instanceOf, Vietnam War operation]
-
A.
event in the Vietnam War
chosen
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.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
-
C.
Pacific War engagement
A Pacific War engagement is a specific military confrontation between opposing forces in the Pacific theater during World War II, encompassing actions in air, sea, and/or land domains.
-
D.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
South Vietnamese general
A South Vietnamese general is a high-ranking military officer who served in the armed forces of the Republic of Vietnam (1955–1975), typically responsible for commanding major units, shaping military strategy, and often playing a significant role in the country’s political affairs during the Vietnam War.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.