Triple
T16336172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVUM |
E396683
|
entity |
| Predicate | missionCapability |
P56184
|
FINISHED |
| Object | multiple engine restarts |
—
|
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: multiple engine restarts | Statement: [AVUM, missionCapability, multiple engine restarts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionCapability Context triple: [AVUM, missionCapability, multiple engine restarts]
-
A.
hasFireMissionCapability
Indicates that an entity possesses the ability to plan, coordinate, or execute fire missions (such as artillery or indirect fire support) as part of combat operations.
-
B.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
C.
operationalCapability
chosen
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
missionCharacteristic
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.