Triple
T4220278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air France Flight 4590 |
E94320
|
entity |
| Predicate | maximumCruisingSpeedOfType |
P2096
|
FINISHED |
| Object | Mach 2.04 |
—
|
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: Mach 2.04 | Statement: [Air France Flight 4590, maximumCruisingSpeedOfType, Mach 2.04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCruisingSpeedOfType Context triple: [Air France Flight 4590, maximumCruisingSpeedOfType, Mach 2.04]
-
A.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
B.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
cruiseSpeed
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
D.
supercruiseCapability
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
-
E.
category1UpperBound_mph
Indicates the maximum speed limit, in miles per hour, that defines the upper boundary of category 1.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.