Triple
T25641793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard |
E642854
|
entity |
| Predicate | capsuleRecoveryMethod |
P19129
|
FINISHED |
| Object | parachutes and retro-thrusters |
—
|
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: parachutes and retro-thrusters | Statement: [New Shepard, capsuleRecoveryMethod, parachutes and retro-thrusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capsuleRecoveryMethod Context triple: [New Shepard, capsuleRecoveryMethod, parachutes and retro-thrusters]
-
A.
capsuleRecovery
Indicates the action or process of retrieving a capsule after its use, mission, or deployment.
-
B.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
C.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
D.
capsuleSystem
Indicates a relationship where an entity functions as or belongs to a capsule-based system (e.g., a system organized around or implemented via capsules).
-
E.
capsuleRecoveryYear
Indicates the calendar year in which a capsule was recovered after its mission or deployment.
- 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_69f5faa11fa88190a7bb53c814995268 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:44 p.m.