Triple
T8555522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Flagship Program |
E202553
|
entity |
| Predicate | budgetClass |
P2120
|
FINISHED |
| Object | multi-billion-dollar missions |
—
|
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: multi-billion-dollar missions | Statement: [NASA Flagship Program, budgetClass, multi-billion-dollar missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetClass Context triple: [NASA Flagship Program, budgetClass, multi-billion-dollar missions]
-
A.
budgetType
chosen
Indicates the classification or category of a budget associated with an entity or financial activity.
-
B.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
C.
budgetLevel
Indicates the relative amount of financial resources allocated or available for something, typically categorized by level (e.g., low, medium, high).
-
D.
budgetRight
Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
-
E.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe88a936c8190a0234bf7da2ff55a |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.