Triple
T25643322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | firstCrewedFlightForCompany |
P2088
|
FINISHED |
| Object | Blue Origin |
—
|
NE NERFINISHED |
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: Blue Origin | Statement: [NS-16 mission, firstCrewedFlightForCompany, Blue Origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrewedFlightForCompany Context triple: [NS-16 mission, firstCrewedFlightForCompany, Blue Origin]
-
A.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
-
B.
performedFirstFlightWith
Indicates that one entity carried out its inaugural or maiden flight in conjunction with, or using, another entity.
-
C.
firstCrewedUSFlightFrom
Indicates that the subject is the first crewed U.S. spaceflight that departed from the specified location.
-
D.
firstFlight
chosen
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
E.
firstCommercialFlight
Indicates that the subject entity operated or was involved in the earliest commercial flight associated with the object entity (such as a route, aircraft type, or service).
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 21, 2026, 5:48 p.m.