Triple
T25786188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block V |
E649422
|
entity |
| Predicate | hasLaunchSystem |
P98190
|
FINISHED |
| Object | 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: torpedo tubes | Statement: [Block V, hasLaunchSystem, torpedo tubes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchSystem Context triple: [Block V, hasLaunchSystem, torpedo tubes]
-
A.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
B.
hasLiftOrLaunchSystem
chosen
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
-
C.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
D.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 22, 2026, 5:55 a.m.