Triple
T20129363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalibr cruise missile |
E490846
|
entity |
| Predicate | launchCanisterType |
P6754
|
FINISHED |
| Object | vertical launch system |
—
|
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: vertical launch system | Statement: [Kalibr cruise missile, launchCanisterType, vertical launch system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchCanisterType Context triple: [Kalibr cruise missile, launchCanisterType, vertical launch system]
-
A.
launcherType
chosen
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
B.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
C.
launchEntity
Indicates initiating the start, deployment, or release of an entity into operation or into a new state or environment.
-
D.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
E.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66760b8f08190a66fbb2e9e3925a3 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.