Triple
T25938253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakthrough Starshot |
E653619
|
entity |
| Predicate | proposedCruisingSpeed |
P10872
|
FINISHED |
| Object | up to 0.2c |
—
|
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: up to 0.2c | Statement: [Breakthrough Starshot, proposedCruisingSpeed, up to 0.2c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedCruisingSpeed Context triple: [Breakthrough Starshot, proposedCruisingSpeed, up to 0.2c]
-
A.
cruiseSpeed
chosen
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
B.
cruiseMachNumber
Indicates the Mach number at which an aircraft typically cruises during normal operation.
-
C.
supercruiseSpeed
Indicates the speed at which an aircraft or vehicle can sustain supersonic flight without using afterburners or additional boost.
-
D.
stallSpeed
Indicates the minimum speed at which an aircraft (or similar vehicle) can fly while still maintaining sufficient lift to avoid stalling.
-
E.
aircraftSpeedClass
Indicates the categorical speed range or performance class to which an aircraft’s speed belongs.
- 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_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 8:40 a.m.