Triple
T37997114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-21 |
E947989
|
entity |
| Predicate | launchVehicleCore |
P164320
|
FINISHED |
| Object | B1058.4 |
—
|
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: B1058.4 | Statement: [SpaceX CRS-21, launchVehicleCore, B1058.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleCore Context triple: [SpaceX CRS-21, launchVehicleCore, B1058.4]
-
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.
launchVehicleComponentOf
chosen
Indicates that one entity is a component or part of a launch vehicle used to send payloads into space.
-
D.
launchVehicleDesignation
Indicates the specific launch vehicle assigned or designated to carry a payload or mission into space.
-
E.
launchVehiclePropulsion
Indicates the propulsion system or method used to generate thrust for a launch vehicle during its ascent or flight.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:20 p.m.