Triple
T22430975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonov An-158 |
E554497
|
entity |
| Predicate | cruiseSpeed_mach |
P90923
|
FINISHED |
| Object | 0.75 |
—
|
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: 0.75 | Statement: [Antonov An-158, cruiseSpeed_mach, 0.75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cruiseSpeed_mach Context triple: [Antonov An-158, cruiseSpeed_mach, 0.75]
-
A.
cruiseMachNumber
chosen
Indicates the Mach number at which an aircraft typically cruises during normal operation.
-
B.
cruiseSpeed
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
C.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
D.
MachNumberRange
Indicates the range of Mach numbers (ratios of an object's speed to the speed of sound) within which a condition, behavior, or specification applies.
-
E.
supercruiseCapability
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.