Triple
T6204832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Solar Probe |
E138720
|
entity |
| Predicate | missionCost |
P4259
|
FINISHED |
| Object | approximately 1.5 billion US dollars |
—
|
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: approximately 1.5 billion US dollars | Statement: [Parker Solar Probe, missionCost, approximately 1.5 billion US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionCost Context triple: [Parker Solar Probe, missionCost, approximately 1.5 billion US dollars]
-
A.
launchCostGoal
Indicates a target or intended cost level associated with launching something (e.g., a product, project, or mission).
-
B.
estimatedCost
chosen
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
C.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
-
D.
acquisitionCost
Indicates the monetary amount or value required to obtain or purchase an entity.
-
E.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.