Triple
T2151681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spitzer Space Telescope |
E47794
|
entity |
| Predicate | deactivationDate |
P14100
|
FINISHED |
| Object | 2020-01-30 |
—
|
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: 2020-01-30 | Statement: [Spitzer Space Telescope, deactivationDate, 2020-01-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivationDate Context triple: [Spitzer Space Telescope, deactivationDate, 2020-01-30]
-
A.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
B.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe4747a0819080e2234f3ea8995f |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.