Triple
T20948416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockwell X-24C |
E515911
|
entity |
| Predicate | intendedSpeedRegime |
P140422
|
FINISHED |
| Object | hypersonic |
—
|
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: hypersonic | Statement: [Rockwell X-24C, intendedSpeedRegime, hypersonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSpeedRegime Context triple: [Rockwell X-24C, intendedSpeedRegime, hypersonic]
-
A.
hasSpeedRegime
chosen
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
-
B.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
C.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
D.
plannedSpeed
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
E.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadab7708190bb3a10bdd3f32d90 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1 p.m.