Triple
T16415093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2 Black Panther |
E398662
|
entity |
| Predicate | specialMunitionCapability |
P76424
|
FINISHED |
| Object | KSTAM top-attack smart munition capable |
—
|
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: KSTAM top-attack smart munition capable | Statement: [K2 Black Panther, specialMunitionCapability, KSTAM top-attack smart munition capable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialMunitionCapability Context triple: [K2 Black Panther, specialMunitionCapability, KSTAM top-attack smart munition capable]
-
A.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
B.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
C.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
D.
weaponFeature
chosen
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
E.
operationalCapability
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3287741008190856882b7f34024fc |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.