Triple
T2389178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-109 |
E48899
|
entity |
| Predicate | EVAObjective |
P30831
|
FINISHED |
| Object | upgrade Hubble Space Telescope power systems |
—
|
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: upgrade Hubble Space Telescope power systems | Statement: [STS-109, EVAObjective, upgrade Hubble Space Telescope power systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAObjective Context triple: [STS-109, EVAObjective, upgrade Hubble Space Telescope power systems]
-
A.
EVAobjective
chosen
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
B.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
EVAcrew
Indicates that the subject is a crew member participating in an extravehicular activity (spacewalk).
-
E.
performedEVA
Indicates that an entity has carried out an extravehicular activity (EVA), such as a spacewalk, outside a spacecraft or space station.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7dca9248190b634ae9e02f6899a |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.