Triple
T25938235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakthrough Starshot |
E653619
|
entity |
| Predicate | proposesSpacecraftType |
P165331
|
FINISHED |
| Object | gram-scale spacecraft |
—
|
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: gram-scale spacecraft | Statement: [Breakthrough Starshot, proposesSpacecraftType, gram-scale spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesSpacecraftType Context triple: [Breakthrough Starshot, proposesSpacecraftType, gram-scale spacecraft]
-
A.
spacecraftTypeSupported
Indicates that a system, facility, or service is capable of accommodating or operating a specified type of spacecraft.
-
B.
spacecraftModel
Indicates that one entity is the specific model or design type of a spacecraft associated with another entity.
-
C.
mentionsSpacecraft
Indicates that one entity makes reference to or discusses a particular spacecraft.
-
D.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
E.
planetaryMissionType
Indicates the specific category or nature of a mission conducted to explore or study a planet or planetary body.
- F. None of above. chosen
Provenance (4 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_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 22, 2026, 8:40 a.m.