Triple
T17179272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiRISE |
E416938
|
entity |
| Predicate | firstScienceImagesDate |
P14316
|
FINISHED |
| Object | 2006-03 |
—
|
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: 2006-03 | Statement: [HiRISE, firstScienceImagesDate, 2006-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstScienceImagesDate Context triple: [HiRISE, firstScienceImagesDate, 2006-03]
-
A.
firstScientificUse
Indicates that an entity represents the earliest known scientific use or application of another entity (such as a concept, method, or technology).
-
B.
firstTelescopicObservationBy
Indicates that the object was the target of the earliest known telescopic observation made by the specified observer.
-
C.
firstOrbitalSuccessDate
Indicates the calendar date on which an entity achieved its first successful orbital mission.
-
D.
firstCloseImagingYear
Indicates the year in which the first close-range imaging (e.g., detailed observational data or images) of the subject was obtained.
-
E.
firstImagesReleaseDate
chosen
Indicates the date on which the first set of images associated with an entity was initially released.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0f9a288190b0ddfb673bd8e84b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.