Triple
T4455347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing T-7A Red Hawk |
E97707
|
entity |
| Predicate | firstFlightAsT-XPrototype |
P28082
|
FINISHED |
| Object | 20 December 2016 |
—
|
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: 20 December 2016 | Statement: [Boeing T-7A Red Hawk, firstFlightAsT-XPrototype, 20 December 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightAsT-XPrototype Context triple: [Boeing T-7A Red Hawk, firstFlightAsT-XPrototype, 20 December 2016]
-
A.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
B.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
C.
inauguralFlightVehicle
Indicates that the subject is the vehicle used to operate the inaugural (first-ever) flight of a given service or route.
-
D.
firstUncrewedTestFlight
Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
-
E.
firstFlownAt
chosen
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f79ca481909338dda9f4f7171f |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.