Triple
T37066797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servicing Mission 3B |
E917466
|
entity |
| Predicate | associatedSpaceTelescope |
P96949
|
FINISHED |
| Object | Hubble Space Telescope |
E7921
|
NE 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: Hubble Space Telescope | Statement: [Servicing Mission 3B, associatedSpaceTelescope, Hubble Space Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSpaceTelescope Context triple: [Servicing Mission 3B, associatedSpaceTelescope, Hubble Space Telescope]
-
A.
spaceTelescope
Indicates a relationship where an entity functions as or is classified as a space-based telescope used for astronomical observation beyond Earth's atmosphere.
-
B.
servicedSpaceTelescope
chosen
Indicates that an entity has performed maintenance or repair operations on a space telescope.
-
C.
usesSpaceTelescope
Indicates that an entity employs or operates a space telescope to carry out its activities or objectives.
-
D.
spacecraftOfMission
Indicates that a given spacecraft is the one used or assigned for a particular mission.
-
E.
countrySpaceAgency
Indicates that a country is the home or governing nation of a particular space agency.
- F. None of above.
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdba8da88190adc2fcd55be49c12 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.