Triple
T25415146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Station |
E636809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vietnam War location |
C15454
|
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 location Context triple: [Yankee Station, instanceOf, Vietnam War location]
-
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.
military region of the Republic of Vietnam
A military region of the Republic of Vietnam was a large territorial command zone responsible for organizing, coordinating, and overseeing military operations, administration, and security within its designated area during the Vietnam War.
-
C.
region of Vietnam
chosen
A region of Vietnam is a large geographic and cultural area within the country, typically defined by shared historical, economic, and environmental characteristics that distinguish it from other parts of Vietnam.
-
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.
People's Army of Vietnam formation
A People's Army of Vietnam formation is an organized military unit or grouping within the PAVN, structured for operational, tactical, or administrative purposes.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:55 p.m.