Triple
T25819524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream GV |
E650360
|
entity |
| Predicate | highSpeedCruise |
P10872
|
FINISHED |
| Object | Mach 0.85 |
—
|
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 0.85 | Statement: [Gulfstream GV, highSpeedCruise, Mach 0.85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highSpeedCruise Context triple: [Gulfstream GV, highSpeedCruise, Mach 0.85]
-
A.
cruiseSpeed
chosen
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
D.
highSpeedBrand
Indicates that a brand is associated with operating or performing at high speed compared to typical or competing brands.
-
E.
hasSpeedRegime
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:28 a.m.