Triple
T22620611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF6-80A |
E558265
|
entity |
| Predicate | thrustReverserCompatibility |
P127053
|
FINISHED |
| Object | target-type thrust reverser systems |
—
|
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: target-type thrust reverser systems | Statement: [CF6-80A, thrustReverserCompatibility, target-type thrust reverser systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustReverserCompatibility Context triple: [CF6-80A, thrustReverserCompatibility, target-type thrust reverser systems]
-
A.
thrustReverserCompatible
chosen
Indicates that a thrust reverser is suitable for use with, and can be properly integrated into, a specific engine or aircraft system.
-
B.
thrustReverserUse
Indicates the action of deploying or using a thrust reverser system to redirect engine thrust, typically to decelerate an aircraft.
-
C.
thrustReverserSupplier
Indicates that one entity is the supplier or provider of the thrust reverser system for another entity (typically an aircraft or engine program).
-
D.
thrustAugmentationMethod
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
-
E.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e383b048190a432c540185916d0 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.