Triple
T9551373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akula-class submarine |
E230427
|
entity |
| Predicate | torpedoTubeConfiguration |
P63128
|
FINISHED |
| Object | 533 mm torpedo tubes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 533 mm torpedo tubes | Statement: [Akula-class submarine, torpedoTubeConfiguration, 533 mm torpedo tubes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torpedoTubeConfiguration Context triple: [Akula-class submarine, torpedoTubeConfiguration, 533 mm torpedo tubes]
-
A.
numberOfTorpedoTubes
Indicates the quantity of torpedo tubes associated with or installed on an entity.
-
B.
torpedoCaliber
chosen
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
C.
missileTubesPerBoat
Indicates the number of missile tubes associated with each individual boat in the relationship.
-
D.
armamentTorpedoes
Indicates that an entity is equipped with torpedoes as part of its armament or weaponry.
-
E.
reducedFromPredecessorMissileTubes
Indicates that an entity has fewer missile tubes than its immediate predecessor in a sequence or class.
- F. None of above.
Provenance (3 batches)
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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd991df7308190a56d95f195627513 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.