Triple
T17121215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RocketMotorOne |
E415468
|
entity |
| Predicate | usedInMissionProfile |
P53282
|
FINISHED |
| Object | ballistic suborbital trajectory |
—
|
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: ballistic suborbital trajectory | Statement: [RocketMotorOne, usedInMissionProfile, ballistic suborbital trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMissionProfile Context triple: [RocketMotorOne, usedInMissionProfile, ballistic suborbital trajectory]
-
A.
usedByMission
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
B.
usedOnMultipleCRSMissions
Indicates that the same item, component, or resource has been employed across more than one CRS (Commercial Resupply Services) mission.
-
C.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
D.
missionProfile
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
-
E.
selectedForMission
Indicates that an entity has been chosen or assigned to participate in a particular 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.