Triple
T10109047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Troops |
E218194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Soviet Navy |
C27419
|
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: branch of the Soviet Navy Context triple: [Coastal Troops, instanceOf, branch of the Soviet Navy]
-
A.
branch of the Soviet Armed Forces
A branch of the Soviet Armed Forces is a major organizational component responsible for a specific domain of military operations—such as ground, naval, air, or strategic missile forces—within the overall Soviet military structure.
-
B.
Soviet Navy cruiser
A Soviet Navy cruiser is a large, fast, heavily armed warship designed by the Soviet Union for surface combat, air defense, and power projection at sea.
-
C.
branch of the Armed Forces of the Russian Federation
A branch of the Armed Forces of the Russian Federation is a major organizational component, such as the Ground Forces, Navy, or Aerospace Forces, with specialized roles, capabilities, and structures for conducting military operations.
-
D.
Imperial Russian Navy formation
An Imperial Russian Navy formation is an organized grouping of naval vessels, aircraft, and supporting units structured under a unified command to conduct maritime operations for the Russian Empire.
-
E.
underwater warfare branch
The underwater warfare branch is a specialized naval division responsible for conducting, coordinating, and supporting military operations beneath the sea, including submarine warfare, mine countermeasures, and undersea surveillance.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.