Triple

T11769133
Position Surface form Disambiguated ID Type / Status
Subject Crew Dragon E279851 entity
Predicate designedForReuseCount P21235 FINISHED
Object multiple flights per capsule 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: multiple flights per capsule | Statement: [Crew Dragon, designedForReuseCount, multiple flights per capsule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForReuseCount
Context triple: [Crew Dragon, designedForReuseCount, multiple flights per capsule]
  • A. designedForReusability chosen
    Indicates that something has been intentionally created or configured so it can be used multiple times without needing to be discarded or fundamentally rebuilt.
  • B. reusedIn
    Indicates that something previously used in one context or instance is used again in another context or instance.
  • C. notReusedFor
    Indicates that something is not used again for a subsequent purpose, context, or instance.
  • D. partiallyReusedAs
    Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
  • E. reusability
    Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
  • 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_69d6ab01d2688190ad8ed6bda487eaa5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a8c2e8b08190a31b1e284fca2aee completed April 10, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69d8a242cd8c819086ed6c5f292dc8cb completed April 10, 2026, 7:09 a.m.
Created at: April 8, 2026, 9:41 p.m.