Triple
T25938233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakthrough Starshot |
E653619
|
entity |
| Predicate | usesPropulsionConcept |
P158578
|
FINISHED |
| Object | photon sail propulsion |
—
|
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: photon sail propulsion | Statement: [Breakthrough Starshot, usesPropulsionConcept, photon sail propulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPropulsionConcept Context triple: [Breakthrough Starshot, usesPropulsionConcept, photon sail propulsion]
-
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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 8:40 a.m.