Triple
T21486123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy midget submarines |
E530120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations vessel |
C43271
|
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: special operations vessel Context triple: [Royal Navy midget submarines, instanceOf, special operations vessel]
-
A.
special-purpose vessel
chosen
A special-purpose vessel is a ship specifically designed and equipped to perform dedicated tasks or services that cannot be efficiently carried out by standard commercial or passenger vessels.
-
B.
specialized maritime unit
A specialized maritime unit is a dedicated team within a naval or coast guard organization trained and equipped to conduct specific high-skill missions at sea, such as search and rescue, interdiction, special operations, or environmental protection.
-
C.
commissioned vessel
A commissioned vessel is a ship or boat that has been formally placed into active service by an authorized organization, typically a navy or government agency, under an official commission.
-
D.
amphibious warfare vessel class
An amphibious warfare vessel class is a group of naval ships designed and equipped to project ground forces from sea to shore, typically carrying troops, vehicles, and landing craft while providing command, control, and logistical support for amphibious operations.
-
E.
motor vessel
A motor vessel is a powered watercraft propelled primarily by engines rather than sails or human effort, used for transporting people, goods, or performing specialized maritime tasks.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:22 p.m.