Triple
T36483166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus 1 |
E898869
|
entity |
| Predicate | launchRocketStage |
P35731
|
FINISHED |
| Object | Saturn I SA-9 |
—
|
NE NERFINISHED |
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: Saturn I SA-9 | Statement: [Pegasus 1, launchRocketStage, Saturn I SA-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchRocketStage Context triple: [Pegasus 1, launchRocketStage, Saturn I SA-9]
-
A.
launchVehicleCoreStage
Indicates the relationship in which a core stage serves as the primary structural and propulsion element of a launch vehicle.
-
B.
launchVehicleStageAbove
Indicates that one launch vehicle stage is positioned above another stage within the same launch vehicle stack.
-
C.
propulsionStage
Indicates a specific phase or stage within a propulsion or thrust-generating process.
-
D.
usesRocketStage
chosen
Indicates that one entity (typically a launch or rocket) employs or incorporates a particular rocket stage as part of its operation or configuration.
-
E.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:10 p.m.