Triple
T20182119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oniks cruise missile |
E492754
|
entity |
| Predicate | launchPlatforms |
P53971
|
FINISHED |
| Object | surface ships |
—
|
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: surface ships | Statement: [Oniks cruise missile, launchPlatforms, surface ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPlatforms Context triple: [Oniks cruise missile, launchPlatforms, surface ships]
-
A.
launchPlatformName
Indicates the name of the platform or site from which a launch (typically of a vehicle, rocket, or mission) is conducted.
-
B.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
C.
appearsInPlatform
Indicates that an entity is present, available, or featured within a particular platform or system.
-
D.
platformsDevelopedFor
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
E.
launchPlatformFor
chosen
Indicates a relationship where one entity serves as the platform or site from which another entity is launched.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.