Triple
T16229636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSS Inspire |
E393944
|
entity |
| Predicate | spaceflightProfile |
P122244
|
FINISHED |
| Object | air-launched suborbital trajectory |
—
|
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: air-launched suborbital trajectory | Statement: [VSS Inspire, spaceflightProfile, air-launched suborbital trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceflightProfile Context triple: [VSS Inspire, spaceflightProfile, air-launched suborbital trajectory]
-
A.
notableAstronautUser
Indicates that the user has a notable or distinguished status specifically as an astronaut.
-
B.
spaceGrantAffiliation
Indicates that an entity is affiliated with, participates in, or is recognized by a space grant program or consortium.
-
C.
astronaut
Indicates that an entity performs the role or activity of traveling and working in space as part of space missions.
-
D.
researchCosmonaut
Indicates that one entity conducts research on, studies, or investigates a cosmonaut.
-
E.
notableCosmonaut
Indicates that the subject is a cosmonaut who is distinguished or well-known for their role, achievements, or significance in spaceflight.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2889688190ac04e4e9479cabf4 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.