Triple
T17334405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF6-80E1A3 |
E420897
|
entity |
| Predicate | thrustReverserCompatible |
P127053
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CF6-80E1A3, thrustReverserCompatible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustReverserCompatible Context triple: [CF6-80E1A3, thrustReverserCompatible, yes]
-
A.
thrustReverserUse
Indicates the action of deploying or using a thrust reverser system to redirect engine thrust, typically to decelerate an aircraft.
-
B.
thrustReverserSupplier
Indicates that one entity is the supplier or provider of the thrust reverser system for another entity (typically an aircraft or engine program).
-
C.
thrustAugmentationMethod
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
-
D.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
E.
landingGearType
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a106df48190a50f96febc13cde7 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.