Triple

T32831124
Position Surface form Disambiguated ID Type / Status
Subject Electron E839690 entity
Predicate reusabilityProgram P21235 FINISHED
Object Electron first stage recovery 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: Electron first stage recovery | Statement: [Electron, reusabilityProgram, Electron first stage recovery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reusabilityProgram
Context triple: [Electron, reusabilityProgram, Electron first stage recovery]
  • A. reusability
    Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
  • B. 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.
  • C. 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.
  • D. reusedIn
    Indicates that something previously used in one context or instance is used again in another context or instance.
  • E. reusabilityMethodUnderStudy
    Indicates that the method being examined or evaluated is specifically under study for its potential or actual reusability.
  • 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_69f3493f22f88190ae6dd4bc15b6cf8d completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6ce6d659881909ddcec1d2966e020 completed May 3, 2026, 4:26 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 1:16 a.m.