Triple

T25938234
Position Surface form Disambiguated ID Type / Status
Subject Breakthrough Starshot E653619 entity
Predicate usesPropulsionConcept P158578 FINISHED
Object ground-based high-power laser array 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: ground-based high-power laser array | Statement: [Breakthrough Starshot, usesPropulsionConcept, ground-based high-power laser array]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesPropulsionConcept
Context triple: [Breakthrough Starshot, usesPropulsionConcept, ground-based high-power laser array]
  • A. propulsionFeature
    Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
  • B. originalPropulsion
    Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
  • C. propulsion
    Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
  • D. propulsionTypeOfSystem chosen
    Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
  • E. hasPropulsionComponent
    Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
  • 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_69e7ab3fd2f881908837305e4ba98011 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f627aedf548190bc9f53c8a2d67b50 completed May 2, 2026, 4:34 p.m.
PD Predicate disambiguation batch_69f623a4e1048190bbb8dd1253fdcee9 completed May 2, 2026, 4:17 p.m.
Created at: April 22, 2026, 8:40 a.m.