Triple
T5561142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Frontiers program |
E145767
|
entity |
| Predicate | costClass |
P18022
|
FINISHED |
| Object | more expensive than Discovery 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: more expensive than Discovery missions | Statement: [New Frontiers program, costClass, more expensive than Discovery missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costClass Context triple: [New Frontiers program, costClass, more expensive than Discovery missions]
-
A.
costModel
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
-
B.
priceCategory
chosen
Indicates the classification of an item or service based on its price level or cost range.
-
C.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
D.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
E.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201857848190a5443b51bcdb63fa |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.