Triple
T32221093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-85 |
E823064
|
entity |
| Predicate | retrievedPayloadInOrbit |
P173852
|
FINISHED |
| Object | CRISTA-SPAS-2 |
—
|
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: CRISTA-SPAS-2 | Statement: [STS-85, retrievedPayloadInOrbit, CRISTA-SPAS-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retrievedPayloadInOrbit Context triple: [STS-85, retrievedPayloadInOrbit, CRISTA-SPAS-2]
-
A.
designedPayloadToLunarOrbit
Indicates that something was created or engineered specifically to deliver a payload into lunar orbit.
-
B.
payloadToTransLunarInjection
Indicates that a payload is being sent onto a trajectory from Earth orbit toward the Moon (trans-lunar injection).
-
C.
firstOrbitalSuccessPayloadType
Indicates the type or category of payload carried on an entity’s first successful orbital mission.
-
D.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
E.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc68a548190b19aaa63d0618d98 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:38 a.m.