Triple
T1598433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51L |
E34336
|
entity |
| Predicate | contributingFactor |
P694
|
FINISHED |
| Object | low launch temperature |
—
|
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: low launch temperature | Statement: [STS-51L, contributingFactor, low launch temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributingFactor Context triple: [STS-51L, contributingFactor, low launch temperature]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
considersFactor
Indicates that one entity takes another entity into account as a factor when forming a judgment, decision, or evaluation.
-
C.
debatedAsCauseOf
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
-
D.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
E.
contributeTo
Indicates that one entity provides support, resources, or effort that helps bring about, enhance, or maintain another entity, outcome, or 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a916d413f08190a4e137e5ed262e25 |
completed | March 5, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69a907bfb39c8190a31e0be14d3d52e6 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.