Triple
T37997151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-21 |
E947989
|
entity |
| Predicate | relatedSpacecraftFamily |
P41743
|
FINISHED |
| Object | Dragon 2 |
E939570
|
NE 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: Dragon 2 | Statement: [SpaceX CRS-21, relatedSpacecraftFamily, Dragon 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSpacecraftFamily Context triple: [SpaceX CRS-21, relatedSpacecraftFamily, Dragon 2]
-
A.
spacecraftFamily
chosen
Indicates that one spacecraft belongs to, or is categorized under, a particular family or series of related spacecraft designs.
-
B.
associatedRocketFamily
Indicates that one entity is related to or belongs to the same rocket family or rocket lineage as another entity.
-
C.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
D.
relatedRocketFamily
Indicates that two rockets are members of the same rocket family or closely related rocket variants.
-
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 (4 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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412cc081888190847c6c0733b483de |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.