Triple
T18768275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 48-1385 |
E458946
|
entity |
| Predicate | achievedMachNumber |
P12248
|
FINISHED |
| Object | approximately Mach 2.3 |
—
|
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: approximately Mach 2.3 | Statement: [48-1385, achievedMachNumber, approximately Mach 2.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedMachNumber Context triple: [48-1385, achievedMachNumber, approximately Mach 2.3]
-
A.
cruiseMachNumber
Indicates the Mach number at which an aircraft typically cruises during normal operation.
-
B.
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.
-
C.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
D.
soundBarrierMachNumber
Indicates the Mach number at which an object reaches or exceeds the speed of sound under given conditions.
-
E.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.