Triple
T17121553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VMS (Virgin Mothership) |
E415477
|
entity |
| Predicate | launchTechnique |
P63810
|
FINISHED |
| Object | captive carry and release |
—
|
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: captive carry and release | Statement: [VMS (Virgin Mothership), launchTechnique, captive carry and release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchTechnique Context triple: [VMS (Virgin Mothership), launchTechnique, captive carry and release]
-
A.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
B.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
C.
launchMass
Indicates the total mass of an object or payload at the moment it is launched.
-
D.
launchMechanism
chosen
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
E.
launchProcedure
Indicates the process or sequence of actions required to initiate or start an operation, system, or mission.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.