Triple
T37720444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpX-DM1 |
E939568
|
entity |
| Predicate | spacecraftVariant |
P64095
|
FINISHED |
| Object | Crew Dragon Demo-1 capsule |
—
|
NE NERFINISHED |
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: Crew Dragon Demo-1 capsule | Statement: [SpX-DM1, spacecraftVariant, Crew Dragon Demo-1 capsule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftVariant Context triple: [SpX-DM1, spacecraftVariant, Crew Dragon Demo-1 capsule]
-
A.
spacecraftModel
Indicates that one entity is the specific model or design type of a spacecraft associated with another entity.
-
B.
usesSpacecraftVariant
chosen
Indicates that one entity employs or operates a specific variant or version of a spacecraft.
-
C.
spacecraftReturnType
Indicates the manner or method by which a spacecraft returns from its mission, such as its return trajectory, mode, or recovery type.
-
D.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
E.
featuresSpacecraft
Indicates that one entity includes, presents, or prominently involves a spacecraft as part of its content, composition, or subject matter.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:18 p.m.