Triple
T10985018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney J58 |
E259605
|
entity |
| Predicate | designedForAltitude |
P60638
|
FINISHED |
| Object | high altitude |
—
|
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 altitude | Statement: [Pratt & Whitney J58, designedForAltitude, high altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForAltitude Context triple: [Pratt & Whitney J58, designedForAltitude, high altitude]
-
A.
operationalAltitude
chosen
Indicates the typical or designated altitude at which an entity is intended to operate.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
D.
cabinPressureAltitude
Indicates the altitude corresponding to the current cabin air pressure, as if that pressure were the standard atmospheric pressure at that height.
-
E.
visibilityAltitude
Indicates the altitude at which something becomes visible or can be seen.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ed1eb88190b7333b746f76a088 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.