Triple
T33094471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRAC |
E846872
|
entity |
| Predicate | isPartOfMission |
P52571
|
FINISHED |
| Object | Spitzer Space Telescope mission |
—
|
NE NERFINISHED |
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: Spitzer Space Telescope mission | Statement: [IRAC, isPartOfMission, Spitzer Space Telescope mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfMission Context triple: [IRAC, isPartOfMission, Spitzer Space Telescope mission]
-
A.
partOfMission
chosen
Indicates that one entity is a component, phase, or element belonging to or included within a larger mission.
-
B.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
C.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
D.
partOfMissionType
Indicates that one entity represents a specific mission type of which the other entity is a constituent or component part.
-
E.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:26 a.m.