Triple
T22134411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULA EELV-class launchers |
E546988
|
entity |
| Predicate | launchServiceType |
P147122
|
FINISHED |
| Object | commercial launch services |
—
|
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: commercial launch services | Statement: [ULA EELV-class launchers, launchServiceType, commercial launch services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchServiceType Context triple: [ULA EELV-class launchers, launchServiceType, commercial launch services]
-
A.
launchServiceEntry
Indicates initiating or starting the provision of a particular service or service instance.
-
B.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
C.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
D.
launchServiceCustomer
Indicates that a customer is the recipient or user of a launch service provided by another entity.
-
E.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
- F. None of above. chosen
Provenance (4 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b8f4248190b6342c8d00942c25 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.