Triple
T26334121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyulka AL-31F |
E662470
|
entity |
| Predicate | thrustVectoringCapability |
P19997
|
FINISHED |
| Object | available on AL-31FP variant |
—
|
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: available on AL-31FP variant | Statement: [Lyulka AL-31F, thrustVectoringCapability, available on AL-31FP variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustVectoringCapability Context triple: [Lyulka AL-31F, thrustVectoringCapability, available on AL-31FP variant]
-
A.
thrustVectorControl
chosen
Indicates the capability to direct or adjust the direction of thrust from a propulsion system to control an object's attitude or trajectory.
-
B.
thrustReverserCompatible
Indicates that a thrust reverser is suitable for use with, and can be properly integrated into, a specific engine or aircraft system.
-
C.
thrustReverserType
Indicates the specific kind of thrust reverser mechanism used to redirect engine thrust, typically on an aircraft.
-
D.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
E.
thrustAugmentationMethod
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6c3954819099a6bda49ff4b598 |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:35 p.m.