Triple
T25361704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGM-88E AARGM |
E635983
|
entity |
| Predicate | operatorCapability |
P39122
|
FINISHED |
| Object | engage time-critical air defense targets |
—
|
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: engage time-critical air defense targets | Statement: [AGM-88E AARGM, operatorCapability, engage time-critical air defense targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCapability Context triple: [AGM-88E AARGM, operatorCapability, engage time-critical air defense targets]
-
A.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
C.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
featuresAbility
Indicates that one entity possesses, includes, or provides a particular ability or capability associated with another entity.
-
E.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 21, 2026, 1:36 p.m.