Triple
T25643380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Origin NS-16 crewed flight |
E642890
|
entity |
| Predicate | capsuleLandingType |
P16151
|
FINISHED |
| Object | parachute-assisted landing |
—
|
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: parachute-assisted landing | Statement: [Blue Origin NS-16 crewed flight, capsuleLandingType, parachute-assisted landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capsuleLandingType Context triple: [Blue Origin NS-16 crewed flight, capsuleLandingType, parachute-assisted landing]
-
A.
typeOfLanding
chosen
Indicates the specific kind or category of landing that occurs in a given event or situation.
-
B.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
C.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
D.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
-
E.
crewLandingStatus
Indicates the status or outcome of a crew’s landing event, such as whether and how the crew has successfully landed.
- 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_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5:48 p.m.