Triple
T10378821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milburn G. Apt |
E244578
|
entity |
| Predicate | testFlightDate |
P93678
|
FINISHED |
| Object | 1956-09-27 |
—
|
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: 1956-09-27 | Statement: [Milburn G. Apt, testFlightDate, 1956-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testFlightDate Context triple: [Milburn G. Apt, testFlightDate, 1956-09-27]
-
A.
testFlight
Indicates that an aircraft or spacecraft is being flown under controlled conditions to evaluate its performance, safety, or functionality before regular use.
-
B.
winningFlightDate
Indicates the date on which the associated flight is determined to be the winning or selected one among a set of candidate flights.
-
C.
fullTransferOfFlightsDate
Indicates that all flights are being moved from one date to another, with the entire schedule transferred to a new date.
-
D.
testFlightCenter
Indicates that an entity serves as a center or facility where test flights are conducted or managed.
-
E.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98fead88190ace49f34b8a27c25 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:03 p.m.