Triple
T7952530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-41C |
E184649
|
entity |
| Predicate | EVApurpose |
P30831
|
FINISHED |
| Object | capture and repair of Solar Maximum Mission |
—
|
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: capture and repair of Solar Maximum Mission | Statement: [STS-41C, EVApurpose, capture and repair of Solar Maximum Mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVApurpose Context triple: [STS-41C, EVApurpose, capture and repair of Solar Maximum Mission]
-
A.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
B.
EVAType
Indicates the type or category of an extravehicular activity (EVA) associated with an entity, specifying what kind of EVA operation or event it represents.
-
C.
EVAobjective
chosen
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
D.
evaCount
Indicates a relationship where a specific count or number is associated with an evaluation-related event, action, or occurrence.
-
E.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5c95908190b6ee900d2b324574 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:10 p.m.