Triple
T15953509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psyche spacecraft |
E386873
|
entity |
| Predicate | missionSelection |
P106644
|
FINISHED |
| Object | selected as a Discovery-class mission in 2017 |
—
|
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: selected as a Discovery-class mission in 2017 | Statement: [Psyche spacecraft, missionSelection, selected as a Discovery-class mission in 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSelection Context triple: [Psyche spacecraft, missionSelection, selected as a Discovery-class mission in 2017]
-
A.
selectedForMission
chosen
Indicates that an entity has been chosen or assigned to participate in a particular mission.
-
B.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
C.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
D.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
-
E.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.