Triple
T32746869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Payload Assist Module |
E837377
|
entity |
| Predicate | orbitChangeCapability |
P110708
|
FINISHED |
| Object | perigee raise |
—
|
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: perigee raise | Statement: [Payload Assist Module, orbitChangeCapability, perigee raise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitChangeCapability Context triple: [Payload Assist Module, orbitChangeCapability, perigee raise]
-
A.
orbitCapability
Indicates that one entity has the ability or suitability to orbit around another entity.
-
B.
orbitalManeuvering
Indicates a controlled change in an object's orbit or trajectory, typically by applying thrust or other forces to alter its path in space.
-
C.
canPerformOrbitReboost
chosen
Indicates that an entity has the capability to execute a maneuver that raises or maintains the orbit of another object in space.
-
D.
orbitalPeriodChange
Indicates a change in the duration of an object's orbital period around another body.
-
E.
deorbitCapability
Indicates the ability of an object (typically a spacecraft or satellite) to intentionally leave orbit and re-enter an atmosphere or otherwise deorbit in a controlled manner.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:12 a.m.