Triple
T8000920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 19 August 1916 |
E186245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I naval engagement |
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 naval engagement Context triple: [Action of 19 August 1916, instanceOf, World War I naval engagement]
-
A.
World War I naval unit
A World War I naval unit is a military formation or vessel grouping organized by a nation's navy during the First World War to conduct maritime operations such as convoy escort, blockade enforcement, fleet engagements, and coastal defense.
-
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 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.
-
D.
maritime attack
A maritime attack is a hostile action conducted against vessels, ports, or other sea-based targets using military, paramilitary, or terrorist means to damage, disrupt, or seize maritime assets.
-
E.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:17 p.m.