Triple
T9418379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscar-class submarine |
E227085
|
entity |
| Predicate | missileCapability |
P75754
|
FINISHED |
| Object | long-range anti-ship cruise missiles |
—
|
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: long-range anti-ship cruise missiles | Statement: [Oscar-class submarine, missileCapability, long-range anti-ship cruise missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileCapability Context triple: [Oscar-class submarine, missileCapability, long-range anti-ship cruise missiles]
-
A.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
B.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
C.
missileTypeCarried
chosen
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
D.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
E.
hasBallisticMissileSubmarine
Indicates that an entity possesses or operates a submarine specifically designed to carry and launch ballistic missiles.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68cd1e3481909abcb715e2398120 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.