Triple
T25641777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard |
E642854
|
entity |
| Predicate | firstSuccessfulFlight |
P126053
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [New Shepard, firstSuccessfulFlight, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulFlight Context triple: [New Shepard, firstSuccessfulFlight, 2015]
-
A.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
B.
firstSuccessfulFlightDesignation
Indicates the specific designation or identifier assigned to an aircraft or spacecraft for its first successful flight.
-
C.
firstWinningFlightDate
chosen
Indicates the date on which the first successful or winning flight associated with the subject occurred.
-
D.
firstPoweredFlightDate
Indicates the calendar date on which an entity (typically an aircraft or spacecraft) achieved its first powered flight.
-
E.
performedFirstFlightWith
Indicates that one entity carried out its inaugural or maiden flight in conjunction with, or using, another entity.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 21, 2026, 5:44 p.m.