Triple
T17894578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Navy Strategic Submarine Forces |
E447399
|
entity |
| Predicate | maintainsCapability |
P32748
|
FINISHED |
| Object | long-range nuclear strike |
—
|
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 nuclear strike | Statement: [Russian Navy Strategic Submarine Forces, maintainsCapability, long-range nuclear strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsCapability Context triple: [Russian Navy Strategic Submarine Forces, maintainsCapability, long-range nuclear strike]
-
A.
providesCapabilityTo
chosen
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
B.
definesCapability
Indicates that one entity specifies or establishes the abilities, functions, or capacities that another entity can possess or perform.
-
C.
replacedCapabilityOf
Indicates that one capability has taken the place of, or superseded, another capability.
-
D.
isPartOfCapability
Indicates that one capability is a component or sub-function within a broader, composite capability.
-
E.
integratesCapability
Indicates that one entity incorporates or combines another entity’s capability into its own functionality.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7ccf808190b4c1fd477043bcc8 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.