Triple
T8882002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauma-class fast attack craft |
E211433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fast attack craft class |
C8502
|
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: fast attack craft class Context triple: [Rauma-class fast attack craft, instanceOf, fast attack craft class]
-
A.
fast attack craft
chosen
A fast attack craft is a small, agile, and heavily armed naval vessel designed for high-speed offensive operations, typically in coastal or littoral waters.
-
B.
nuclear-powered fast attack submarine class
A nuclear-powered fast attack submarine class is a group of submarines designed for high-speed, long-endurance underwater operations focused on hunting enemy submarines and surface ships, intelligence gathering, and supporting naval strike missions.
-
C.
battlecruiser class
A battlecruiser class represents a large, fast, heavily armed warship optimized for long-range offensive power at the expense of some armor protection compared to battleships.
-
D.
surface combatant class
A surface combatant class is a category of naval warships designed and equipped to engage enemy forces on or near the sea surface using a combination of offensive and defensive weapon systems.
-
E.
force carrier
A force carrier is a particle or entity that mediates interactions between other particles, transmitting fundamental forces such as electromagnetism, the strong force, or the weak force.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:53 p.m.