Triple
T9179787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney F119 |
E220291
|
entity |
| Predicate | thrustVectoringAxis |
P24153
|
FINISHED |
| Object | pitch |
—
|
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: pitch | Statement: [Pratt & Whitney F119, thrustVectoringAxis, pitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustVectoringAxis Context triple: [Pratt & Whitney F119, thrustVectoringAxis, pitch]
-
A.
thrustVectorControl
Indicates the capability to direct or adjust the direction of thrust from a propulsion system to control an object's attitude or trajectory.
-
B.
thrustControl
Indicates a relationship where one entity regulates or adjusts the thrust output or propulsion force of another entity.
-
C.
thrustReverserUse
Indicates the action of deploying or using a thrust reverser system to redirect engine thrust, typically to decelerate an aircraft.
-
D.
thrustReverserSupplier
Indicates that one entity is the supplier or provider of the thrust reverser system for another entity (typically an aircraft or engine program).
-
E.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc25064588190856c96b229d9cd60 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.