Triple
T33924579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sud Aviation Super-Caravelle |
E869712
|
entity |
| Predicate | intendedCruisingSpeed |
P34087
|
FINISHED |
| Object | supersonic |
—
|
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: supersonic | Statement: [Sud Aviation Super-Caravelle, intendedCruisingSpeed, supersonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCruisingSpeed Context triple: [Sud Aviation Super-Caravelle, intendedCruisingSpeed, supersonic]
-
A.
cruiseSpeed
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
B.
cruiseMachNumber
Indicates the Mach number at which an aircraft typically cruises during normal operation.
-
C.
stallSpeed
Indicates the minimum speed at which an aircraft (or similar vehicle) can fly while still maintaining sufficient lift to avoid stalling.
-
D.
supercruiseSpeed
chosen
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
E.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:49 a.m.