Parchim-class corvette
Enable an agent to identify Parchim-class corvettes, distinguish their variants and individual vessels, and assess documented configuration, condition and suitability for authorized service or preservation.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 16 findings · 24 questions
Class and hull identity Establish what the Parchim name denotes and how individual vessels remain identifiable.
Project and variant boundaries
Relate Parchim terminology to documented design variants.
Designation crosswalk
Record project designations exactly as sources use them and distinguish verified equivalence from provisional mappings.
- Which authoritative records map Parchim I and Parchim II to their project designations? definition
- Does this registry entry cover both variants, or does its originating record identify a narrower class? boundary
Individual vessel continuity
Track class members through renaming, renumbering and transfer.
Persistent hull identity
Use construction identity and dated documentary links to connect successive names without relying on pennant numbers alone.
- Which builder record or construction number anchors this vessel's membership in the Parchim class? provenance
- What records establish continuity between its earlier and later names or pennant numbers? provenance
Variant configuration Describe the physical baseline and equipment differences that matter when assessing a Parchim-class hull.
Hull and machinery baseline
Associate dimensions and propulsion information with a defined variant and loading condition.
Applicable platform specification
Keep class design figures, variant specifications and individual survey measurements distinct.
- Which dimensions, displacement conditions and propulsion arrangement are documented for this vessel's specific Parchim variant? measurement
- Which reported figures describe design intent, acceptance trials or a later hull survey? provenance
Mission equipment and refits
Track sensors and armament as dated configurations.
Verified equipment fit
Record the sonar, radar, guns and antisubmarine equipment actually supported by evidence for the variant or hull, including removals and replacements.
- Which sensor and armament installations distinguish this variant from the other Parchim variant? boundary
- Which dated plans, inventories or photographs substantiate the vessel's configuration after each refit? provenance
Condition and service suitability Separate nominal class capability from the assessed condition of an individual vessel.
Mobility and seaworthiness
Connect vessel movement decisions to hull condition, propulsion availability and applicable restrictions.
Survey-supported operating envelope
Use current surveys and trials to qualify design figures for speed, draught, endurance and machinery availability.
- What dated hull, propulsion and steering assessments establish this Parchim's present movement restrictions? measurement
- What additional inspection or certification is required before an authorized voyage, tow or docking? action
Installed system availability
Assess the difference between visible equipment, functioning equipment and supported equipment.
Configuration versus readiness
An equipment listing establishes a claimed fit; separate evidence is needed for serviceability, support and qualified operation.
- Which installed propulsion, navigation and mission systems have dated serviceability evidence, and which remain unverified? measurement
- Which documented shortages in parts, technical records or qualified personnel constrain upkeep of this configuration? action
Service history and disposition Track operator changes, modifications and the eventual disposition of each class member.
Operator and refit history
Connect dated operator records to configuration changes.
Transfer-linked configuration history
Treat transfer, renaming and refit as separate events; one does not establish that the others occurred.
- Which records establish each operator's custody dates for this particular Parchim hull? provenance
- What equipment or structural changes are documented around transfer, and which are merely assumed from the new operator? boundary
Retirement and permitted use
Distinguish administrative retirement from physical condition and final disposition.
Evidenced disposition
Record reserve, decommissioning, preservation, loss or dismantling only with dated hull-specific evidence, and identify unresolved custody or condition.
- What is the latest evidenced status of this hull, and does it describe administrative standing or physical disposition? provenance
- What custody, demilitarization and condition evidence is required for its proposed preservation, transfer or dismantling? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these typical measurements hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Parchim-class corvette this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
What it is Filled
The Parchim-class corvette is a class of small diesel-powered anti-submarine warships designed and built in East Germany for coastal operations, comprising Project 1331 and the related Soviet export variant Project 1331M.
In scope
- Class membership, project designations and the boundary between Parchim I and Parchim II.
- Hull identity across changes of ship name, pennant number and operator.
- Variant-specific hull, propulsion, sensor and armament configurations.
- Evidence needed to assess seaworthiness, equipment availability and maintenance needs.
- Configuration changes and transitions between service, reserve, preservation and disposal.
Out of scope
- General properties shared by all corvettes and naval vessels.
- Independent engineering models of installed engines, sonar, radar and weapons.
- Naval organizations, command structures and national defense policy.
- Tactical employment, targeting and weapon firing procedures.
- The city of Parchim and unrelated objects sharing its name.
Why it exists Filled
Enable an agent to identify Parchim-class corvettes, distinguish their variants and individual vessels, and assess documented configuration, condition and suitability for authorized service or preservation.
Distinguishing features Filled
- Require documentary class or project identification rather than accepting the generic label 'corvette'; the shipbuilder group's historical portfolio explicitly lists Parchim-class corvettes. [NVL portfolio](https://nvl.de/sites/default/files/2021-12/NVL-Naval-Solutions-Brochure-2021-EN.pdf)
- Treat Project 1331M as a documented Parchim designation while requiring further evidence to resolve its relationship to Project 133.1 and the Parchim I/II labels. [FOI Baltic Fleet study](https://www.foi.se/rest-api/report/FOI-R--5119--SE)
- Distinguish a member of the class from the vessel named Parchim: a shared name alone establishes neither class membership nor hull identity.
- Distinguish a refitted Parchim from a different class through construction identity and documented conversion history, rather than judging only by its current guns or mast arrangement.
- Reject organism-oriented interpretation of PHY.LIV: the relevant identifying evidence concerns a ship design and manufactured hulls, not taxonomy, life stages or populations.
What robots and AI may and may not do Filled
Must not
- Assist in targeting, tracking or attacking a ship or its crew.
- Present contested claims about a ship's status or location as fact.
- Spread fabricated imagery or reports about naval operations.
- Disclose non-public operational details obtained without authority.
Only with a human decision
- Publishing the position or movements of a warship in an ongoing conflict.
- Attributing a specific incident to a named hull.
May
- Identify ships of this class and their variants from published records and features.
- Report the service history and current operator of individual hulls from reliable sources.
- Distinguish class design data from the condition of a particular ship.
Moral aspects Filled
- Warships passed between states carry political history and present-day security stakes.
- Misinformation about naval forces can raise tensions.
Who is affected
- Crews
- Coastal communities
- People affected by naval operations
Owners Filled
Steward
The navy of the operating state for each ship.
Master systems
- Naval vessel registers of the operating state
Links to other meta-models Filled
parent
- Q18926983 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.parchim-class-corvette
- Wikidata: Q699713 (https://www.wikidata.org/wiki/Q699713)
Direct properties required Filled
- Class and project designation: Parchim I; Parchim II; source-recorded project designation; unresolved
- Hull identity and class membership: Builder and construction number linked to dated names, pennant numbers and class evidence
- Configuration baseline: Hull or variant linked to an as-built or refitted configuration and effective date
- Principal dimensions and displacement: Length, beam and draught in m; displacement in t with loading condition
- Propulsion installation and availability: Documented machinery arrangement; available, restricted, unavailable or unknown by subsystem
- Speed, range and endurance: Speed in kn; range in nautical miles at stated speed; endurance in days under stated conditions
- Sensor and armament fit: Installed system identities, positions, quantities and dated installation or removal evidence
- Service and material condition: Dated administrative status plus separately evidenced hull, machinery and safety-system condition
Recognition required Filled
- Small corvette with a compact superstructure and anti-submarine weapons forward.
- Pennant number and name distinguish individual ships.
- Variant differences show in masts, sensors and armament fit.
Capabilities and actions required Filled
- Match a vessel record to the Parchim class and identify unresolved variant evidence.
- Reconcile renamed or transferred vessels without duplicating physical hulls.
- Compare a hull's documented equipment against its applicable variant and refit baseline.
- Flag missing inspections, unsupported performance claims and incompatible configuration assumptions.
- Prepare evidence requirements for authorized maintenance, survey, preservation or disposal decisions.
Hazards and failure modes required Filled
- Ageing hulls and machinery raise the risk of fire and flooding.
- Stored munitions create explosion hazards on board and in port.
- Scrapping releases hazardous materials if not controlled.
Standards and interfaces required Filled
- Convention on the International Regulations for Preventing Collisions at Sea (COLREGs), International Maritime Organization.
Context of use required Filled
- Parchim-class corvettes were developed for coastal anti-submarine operations and associated naval patrol duties.
- They are encountered in naval service records, ship identification references and histories of East German and Soviet fleet procurement.
- Assessment of an individual vessel requires records of its variant, subsequent modifications and current condition.
Sources Filled
- Wikidata item Q699713: Parchim-class corvette - identity and sense of the item
- Wikipedia: Parchim-class corvette - general description of the item
Open questions
- Does the originating registry record intend the whole Parchim family or specifically Parchim I, and is an existing world model already authoritative for that scope?
- What registry domain should replace or qualify PHY.LIV for this manufactured naval vessel?
- Which primary design or navy records settle the exact mapping of Project 133.1, Project 1331M and Parchim I/II terminology?
- Which authoritative variant specifications and hull-specific refit records establish machinery, sensor and armament differences without mixing configurations?
- What dated operator or disposal records establish the present status of each surviving hull, and where must status remain unknown?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q699713/spec.json