Triple
T32257157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason-1 |
E824054
|
entity |
| Predicate | endOfLifeReason |
P174985
|
FINISHED |
| Object | risk from space debris |
—
|
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: risk from space debris | Statement: [Jason-1, endOfLifeReason, risk from space debris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfLifeReason Context triple: [Jason-1, endOfLifeReason, risk from space debris]
-
A.
endOfLife
Indicates that an entity has reached the termination point of its existence, lifecycle, or functional use.
-
B.
endOfLifeDate
Indicates the date on which an entity’s existence, validity, or operational life comes to an end.
-
C.
endOfSupportApprox
Indicates that the support period for something is expected to end around a particular time, but the exact end date is approximate rather than precise.
-
D.
endOfExtendedSupport
Indicates the point in time when extended support for something (such as a product or service) is officially terminated.
-
E.
endOfLongTermSupportDate
Indicates the calendar date on which long-term support for a product, service, or version officially ends.
- F. None of above. chosen
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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 12:41 a.m.