Triple
T23535522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star 48BV |
E576689
|
entity |
| Predicate | orbitInjectionRole |
P52887
|
FINISHED |
| Object | performs final velocity increment |
—
|
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: performs final velocity increment | Statement: [Star 48BV, orbitInjectionRole, performs final velocity increment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitInjectionRole Context triple: [Star 48BV, orbitInjectionRole, performs final velocity increment]
-
A.
orbitInjectionMethod
Indicates the method or technique used to insert an object into a specific orbit.
-
B.
spaceStationRole
Indicates the functional role or duty an entity has in relation to a space station.
-
C.
orbitalInsertionAround
Indicates the action or event of placing an object into a stable orbit around another body.
-
D.
launchVehicleRole
chosen
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
-
E.
orbitInsertionAttempt
Indicates an attempt to place an object into a stable orbit around a celestial body.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae164f348190a6bde1a0dfc66389 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.