Triple
T6842052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. bombing of Cambodia |
E157796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Vietnam War era |
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: event in the Vietnam War era Context triple: [U.S. bombing of Cambodia, instanceOf, event in the Vietnam War era]
-
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.
event in the Civil Rights Movement
An event in the Civil Rights Movement is a historically specific occurrence—such as a protest, march, court decision, or legislative action—that contributed to the struggle against racial segregation and discrimination in the United States.
-
C.
event in the Indonesian National Revolution
A historically significant occurrence, such as a battle, political decision, diplomatic action, or social upheaval, that took place between 1945 and 1949 and influenced the course or outcome of the Indonesian National Revolution.
-
D.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
-
E.
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.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:19 p.m.