Triple
T10903540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of the RMS Lusitania |
E257507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval incident of World War I |
C8362
|
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: naval incident of World War I Context triple: [sinking of the RMS Lusitania, instanceOf, naval incident of World War I]
-
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.
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.
-
C.
naval theatre of war
A naval theatre of war is a maritime region, including its adjacent coastal areas and airspace, where naval forces conduct coordinated military operations during an armed conflict.
-
D.
naval raid
A naval raid is a swift, targeted maritime operation conducted by warships or naval forces to strike enemy assets, disrupt activities, or gather intelligence, typically without the intention of holding territory.
-
E.
maritime incident
chosen
A maritime incident is any unexpected or unintended event involving a vessel or marine operation that compromises or threatens safety, the environment, property, or normal navigation at sea or in navigable waters.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.