Triple
T38239952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Hush |
E1013733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I operation |
C20682
|
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: World War I operation Context triple: [Operation Hush, instanceOf, World War I operation]
-
A.
World War I military operation
chosen
A World War I military operation is a coordinated set of strategic and tactical actions conducted by armed forces during the First World War to achieve specific military objectives within a defined time and geographic area.
-
B.
World War I battle
A World War I battle is a large-scale, often prolonged military engagement between opposing forces during the 1914–1918 global conflict, characterized by trench warfare, industrialized weaponry, and significant casualties.
-
C.
World War I military formation
A World War I military formation is an organized grouping of soldiers, equipment, and command structures arranged for combat operations according to the tactical doctrines and technological constraints of the 1914–1918 conflict.
-
D.
aspect of World War I
An aspect of World War I is a distinct thematic element—such as military strategy, technological innovation, political diplomacy, social impact, or cultural memory—that characterizes and helps explain the nature and consequences of the conflict.
-
E.
World War I air operations
World War I air operations encompass the use of aircraft for reconnaissance, air combat, bombing, and support missions that transformed military strategy and technology in the early 20th century.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.