Triple
T16370709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-51A Waverider |
E397555
|
entity |
| Predicate | firstFlightRole |
P38969
|
FINISHED |
| Object | scramjet flight test |
—
|
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: scramjet flight test | Statement: [X-51A Waverider, firstFlightRole, scramjet flight test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightRole Context triple: [X-51A Waverider, firstFlightRole, scramjet flight test]
-
A.
firstFlightCommander
Indicates that one entity served as the first commander in charge of another entity’s inaugural flight.
-
B.
firstFlightType
chosen
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
C.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
D.
firstFlownOn
Indicates the date or time at which something (typically an aircraft or spacecraft) made its initial flight.
-
E.
firstFlightBody
Indicates that the subject entity is the first aircraft or spacecraft body used for a particular flight or mission.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff414d808190beae2ff162e430f8 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.