Triple

T15829850
Position Surface form Disambiguated ID Type / Status
Subject Missions of Opportunity E383840 entity
Predicate costCap P60454 FINISHED
Object lower than full Explorer 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: lower than full Explorer missions | Statement: [Missions of Opportunity, costCap, lower than full Explorer missions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: costCap
Context triple: [Missions of Opportunity, costCap, lower than full Explorer missions]
  • A. fareCapping
    Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
  • B. costModel
    Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
  • C. estimatedCost
    Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
  • D. capped chosen
    Indicates that one entity has placed a limit or maximum boundary on another entity’s quantity, value, or extent.
  • E. hasCost
    Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e11e636bb48190a6b39feb550aaa3d completed April 16, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.