Triple
T9252629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta-class submarine |
E222360
|
entity |
| Predicate | missileLaunchCapability |
P87792
|
FINISHED |
| Object | underwater launch |
—
|
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: underwater launch | Statement: [Delta-class submarine, missileLaunchCapability, underwater launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileLaunchCapability Context triple: [Delta-class submarine, missileLaunchCapability, underwater launch]
-
A.
missileTypeCarried
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
B.
hasFireMissionCapability
Indicates that an entity possesses the ability to plan, coordinate, or execute fire missions (such as artillery or indirect fire support) as part of combat operations.
-
C.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
D.
missileWeight
Indicates the weight or mass associated with a missile in the relationship.
-
E.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
- F. None of above. chosen
Provenance (4 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b0789481908e8e44ebf1b3c713 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:31 p.m.