Triple
T11692650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocketplane Kistler |
E277905
|
entity |
| Predicate | vehicleRecoveryMethod |
P19129
|
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: [Rocketplane Kistler, vehicleRecoveryMethod, parachute-assisted landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRecoveryMethod Context triple: [Rocketplane Kistler, vehicleRecoveryMethod, parachute-assisted landing]
-
A.
pullsVehicle
Indicates that one entity exerts force to draw or tow a vehicle from one place to another.
-
B.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
C.
relaunchVehicle
Indicates restarting or sending a vehicle back into operation after it has been stopped, deactivated, or previously launched.
-
D.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
E.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.