Triple
T32213372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Servicing Mission 2 |
E822864
|
entity |
| Predicate | upgradedSubsystem |
P92626
|
FINISHED |
| Object | Fine Guidance Sensors |
—
|
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: Fine Guidance Sensors | Statement: [Hubble Servicing Mission 2, upgradedSubsystem, Fine Guidance Sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedSubsystem Context triple: [Hubble Servicing Mission 2, upgradedSubsystem, Fine Guidance Sensors]
-
A.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
-
B.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
C.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
D.
upgradedStatusTo
Indicates that one entity has changed another entity’s status or level to a higher or more advanced state.
-
E.
underwentUpgrade
chosen
Indicates that an entity has experienced an improvement or enhancement process that changed it to a newer or more advanced state.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb94ce188190b3196b0cc902b051 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.