Triple
T30708013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW5000 |
E781805
|
entity |
| Predicate | designedForSupercruiseSupport |
P34086
|
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: [PW5000, designedForSupercruiseSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForSupercruiseSupport Context triple: [PW5000, designedForSupercruiseSupport, yes]
-
A.
supercruiseCapability
chosen
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
-
B.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
C.
isSupersonicAircraft
Indicates that an aircraft is capable of flying faster than the speed of sound.
-
D.
thrustReverserCompatible
Indicates that a thrust reverser is suitable for use with, and can be properly integrated into, a specific engine or aircraft system.
-
E.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 29, 2026, 8:35 p.m.