Triple
T4065760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMRTG |
E86318
|
entity |
| Predicate | powerDegradation |
P8109
|
FINISHED |
| Object | declines over mission lifetime |
—
|
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: declines over mission lifetime | Statement: [MMRTG, powerDegradation, declines over mission lifetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDegradation Context triple: [MMRTG, powerDegradation, declines over mission lifetime]
-
A.
degradationMechanism
Indicates the process or mechanism by which something deteriorates, breaks down, or loses its original quality or function over time.
-
B.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
C.
lostPowerDuring
Indicates that an entity ceased to have electrical or functional power at some time during a specified event or interval.
-
D.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
E.
powerDecline
chosen
Indicates a decrease or weakening in the level, intensity, or effectiveness of power exerted or possessed in a given context.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.