Triple
T25643002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard booster |
E642881
|
entity |
| Predicate | landingProfile |
P158952
|
FINISHED |
| Object | vertical powered 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: vertical powered landing | Statement: [New Shepard booster, landingProfile, vertical powered landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingProfile Context triple: [New Shepard booster, landingProfile, vertical powered landing]
-
A.
landingProfile
chosen
Indicates the specific way in which an entity arrives at or touches down on a surface or destination, including its approach and contact characteristics.
-
B.
landingPilot
Indicates that an entity is acting as the pilot responsible for landing an aircraft or spacecraft.
-
C.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
D.
profile
Indicates that one entity creates, presents, or analyzes a detailed description or representation of another entity’s characteristics or behavior.
-
E.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
- 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_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 5:46 p.m.