Triple
T14693778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astute programme |
E345100
|
entity |
| Predicate | armamentLaunchSystem |
P101195
|
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: [Astute programme, armamentLaunchSystem, 533 mm torpedo tubes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentLaunchSystem Context triple: [Astute programme, armamentLaunchSystem, 533 mm torpedo tubes]
-
A.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
-
B.
armamentConfiguration
chosen
Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given context.
-
C.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
D.
primaryArmamentLayout
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
E.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.