Triple

T25664495
Position Surface form Disambiguated ID Type / Status
Subject BE-4 E643473 entity
Predicate designedForReusabilityCycles P21235 FINISHED
Object multiple flights per engine 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 engine | Statement: [BE-4, designedForReusabilityCycles, multiple flights per engine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForReusabilityCycles
Context triple: [BE-4, designedForReusabilityCycles, multiple flights per engine]
  • 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. reusability
    Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
  • C. reusabilityImpact
    Indicates how the ability to reuse something (such as a component, resource, or design) affects outcomes, performance, or other relevant factors in a given context.
  • D. maxDesignReuses
    Indicates the maximum number of times a given design can be reused within a specified context or system.
  • E. reusedIn
    Indicates that something previously used in one context or instance is used again in another context or instance.
  • 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_69e77e7e45648190a068ed3faa8016ea completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f661b58ac48190907b6c6e9ccc2c59 completed May 2, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69f660eea4648190b0d5e24293607813 completed May 2, 2026, 8:39 p.m.
Created at: April 21, 2026, 7 p.m.