Triple
T8536356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM-9 Sidewinder |
E202085
|
entity |
| Predicate | AIM-9XFeature |
P76424
|
FINISHED |
| Object | thrust vectoring control |
—
|
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: thrust vectoring control | Statement: [AIM-9 Sidewinder, AIM-9XFeature, thrust vectoring control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AIM-9XFeature Context triple: [AIM-9 Sidewinder, AIM-9XFeature, thrust vectoring control]
-
A.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
B.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
C.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
D.
weaponFeature
chosen
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
E.
fireControlFeature
Indicates a relationship where an entity possesses or is associated with a capability or mechanism for directing, managing, or controlling the use of fire or weapon fire.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a3f024819095d560a205ff1c75 |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.