Triple
T25475137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strela-2 |
E638410
|
entity |
| Predicate | systemWeightReadyToFire |
P164171
|
FINISHED |
| Object | about 15 kilograms |
—
|
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: about 15 kilograms | Statement: [Strela-2, systemWeightReadyToFire, about 15 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemWeightReadyToFire Context triple: [Strela-2, systemWeightReadyToFire, about 15 kilograms]
-
A.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
B.
totalReadyToFireMissiles
Indicates the total number of missiles that are currently prepared and available to be launched.
-
C.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
D.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
E.
firingPlatform
Indicates a platform or structure from which a weapon or projectile is launched or fired.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 21, 2026, 2:25 p.m.