Triple
T32820584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-31 Hubble deployment |
E839423
|
entity |
| Predicate | missionNumberOfDiscovery |
P26361
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [STS-31 Hubble deployment, missionNumberOfDiscovery, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionNumberOfDiscovery Context triple: [STS-31 Hubble deployment, missionNumberOfDiscovery, 10]
-
A.
missionTypeOnMaidenVoyage
Indicates the type or nature of the mission specifically during an entity’s maiden (first) voyage.
-
B.
firstMajorScientificExploration
Indicates that an entity represents the earliest significant scientific investigation or expedition undertaken by another entity.
-
C.
missionNumber
chosen
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
-
D.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
E.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:15 a.m.