Triple
T12681444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Lunar Payload Services |
E302955
|
entity |
| Predicate | contractCeiling |
P75040
|
FINISHED |
| Object | up to 2.6 billion USD |
—
|
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: up to 2.6 billion USD | Statement: [Commercial Lunar Payload Services, contractCeiling, up to 2.6 billion USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractCeiling Context triple: [Commercial Lunar Payload Services, contractCeiling, up to 2.6 billion USD]
-
A.
ceilingBasedOn
Indicates that one entity’s maximum limit or upper bound is determined or constrained by another entity.
-
B.
maximumCeiling
chosen
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
C.
ceiling
Indicates that one entity is the smallest value that is greater than or equal to another value, typically representing a rounding-up operation.
-
D.
hasCeilingType
Indicates that an entity is associated with or characterized by a specific type of ceiling.
-
E.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b32dbc81908101fc5f07e26ed3 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.