Triple
T3729195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astrophysics Explorers Program |
E79020
|
entity |
| Predicate | costPolicy |
P17476
|
FINISHED |
| Object | cost-capped 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: cost-capped missions | Statement: [NASA Astrophysics Explorers Program, costPolicy, cost-capped missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costPolicy Context triple: [NASA Astrophysics Explorers Program, costPolicy, cost-capped missions]
-
A.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
B.
costModel
chosen
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
-
C.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
-
D.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
E.
subscriptionPolicy
Indicates the rules, terms, and conditions that govern how a subscription is obtained, used, renewed, or terminated between parties.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.