Triple
T146024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypersonic Technology Vehicle programs |
E3331
|
entity |
| Predicate | flightRegime |
P5432
|
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: [Hypersonic Technology Vehicle programs, flightRegime, hypersonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightRegime Context triple: [Hypersonic Technology Vehicle programs, flightRegime, hypersonic]
-
A.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
FAAcode
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
-
C.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
D.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
E.
cockpitType
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
- F. None of above. chosen
Provenance (4 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ea7eac8190884a53453a9e0dd6 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a25656a4fc81908a87678ac3d28f93 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.