Triple
T34952570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block I stage |
E1008038
|
entity |
| Predicate | launchProfilePhase |
P22825
|
FINISHED |
| Object | final ascent to orbital velocity |
—
|
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: final ascent to orbital velocity | Statement: [Block I stage, launchProfilePhase, final ascent to orbital velocity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchProfilePhase Context triple: [Block I stage, launchProfilePhase, final ascent to orbital velocity]
-
A.
launchProfile
Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
-
B.
launchProcedure
Indicates the process or sequence of actions required to initiate or start an operation, system, or mission.
-
C.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
launchStatus
Indicates the current state or phase of a launch process, such as whether it is planned, in progress, successful, or failed.
-
E.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4 p.m.