Triple
T10197016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Near Infrared Camera and Multi-Object Spectrometer |
E238787
|
entity |
| Predicate | deactivatedDate |
P14100
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Near Infrared Camera and Multi-Object Spectrometer, deactivatedDate, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivatedDate Context triple: [Near Infrared Camera and Multi-Object Spectrometer, deactivatedDate, 1999]
-
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.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
C.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
D.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
dateOfAbandonment
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedcaf6688190938d8e56e29493eb |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.