Triple
T3834133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSS Unity |
E91086
|
entity |
| Predicate | crewLaunchAndLandingMode |
P12133
|
FINISHED |
| Object | horizontal takeoff and 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: horizontal takeoff and landing | Statement: [VSS Unity, crewLaunchAndLandingMode, horizontal takeoff and landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLaunchAndLandingMode Context triple: [VSS Unity, crewLaunchAndLandingMode, horizontal takeoff and landing]
-
A.
aircraftLaunchAndRecovery
Indicates the relationship in which an aircraft is launched from and/or recovered by a platform, facility, or system.
-
B.
plannedLandingMethod
chosen
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
C.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
D.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
E.
landingMethodFirstStage
Indicates the method by which the first stage of a launch vehicle returns and lands after separation.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.