Triple
T33151790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Nürnberg sunk |
E848456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I naval event |
C61491
|
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 event Context triple: [SMS Nürnberg sunk, instanceOf, World War I naval event]
-
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 II naval disaster
A World War II naval disaster is a catastrophic maritime event during the Second World War in which warships or naval convoys suffered significant loss of life, vessels, or strategic capability due to combat, accidents, or environmental conditions.
-
D.
World War I military operation
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.
-
E.
World War I home front event
A World War I home front event is any significant occurrence, activity, or policy within a nation’s civilian sphere during the war that reflects or affects its social, economic, political, or cultural mobilization for the conflict.
- F. None of above. chosen
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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.