Triple
T4119127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mach number |
E90366
|
entity |
| Predicate | typicalRangeHypersonic |
P13474
|
FINISHED |
| Object | M ≥ 5 |
—
|
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: M ≥ 5 | Statement: [Mach number, typicalRangeHypersonic, M ≥ 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRangeHypersonic Context triple: [Mach number, typicalRangeHypersonic, M ≥ 5]
-
A.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
B.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
supercruiseCapability
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
-
D.
temperature_upperAtmosphere
Indicates the temperature measured or present in the upper layers of an atmosphere.
-
E.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.