Triple
T25641779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard |
E642854
|
entity |
| Predicate | firstHumanFlight |
P191769
|
FINISHED |
| Object | 2021-07-20 |
—
|
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: 2021-07-20 | Statement: [New Shepard, firstHumanFlight, 2021-07-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHumanFlight Context triple: [New Shepard, firstHumanFlight, 2021-07-20]
-
A.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
B.
performedFirstFlightWith
Indicates that one entity carried out its inaugural or maiden flight in conjunction with, or using, another entity.
-
C.
placeOfFirstPoweredFlight
Indicates the location where an entity achieved its first successful powered flight.
-
D.
firstSuccessfulFlightDesignation
Indicates the specific designation or identifier assigned to an aircraft or spacecraft for its first successful flight.
-
E.
firstToLand
Indicates that the subject is the earliest or initial entity to arrive at or touch down on a particular place or surface.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 21, 2026, 5:44 p.m.