Triple
T20703874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney JT10D |
E508848
|
entity |
| Predicate | bypassRatioCategory |
P15528
|
FINISHED |
| Object | high-bypass |
—
|
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: high-bypass | Statement: [Pratt & Whitney JT10D, bypassRatioCategory, high-bypass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bypassRatioCategory Context triple: [Pratt & Whitney JT10D, bypassRatioCategory, high-bypass]
-
A.
bypassRatio
chosen
Indicates the proportion between the mass flow of air that bypasses the engine core and the mass flow that passes through the core in a turbofan or similar propulsion system.
-
B.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
C.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
D.
bypassedVia
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
-
E.
bypassName
Indicates that an entity is known or referred to by an alternative name used specifically for bypassing or circumventing a standard process, route, or restriction.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18dbda081908217dcb61cbf7ba4 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.