Triple
T32831131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron |
E839690
|
entity |
| Predicate | launchService |
P7206
|
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: [Electron, launchService, commercial launch services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchService Context triple: [Electron, launchService, commercial launch services]
-
A.
launchServiceType
Indicates the type or category of launch service associated with an entity, such as the kind of launch operation or offering it provides.
-
B.
launchServiceEntry
Indicates initiating or starting the provision of a particular service or service instance.
-
C.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
D.
launchProvider
chosen
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
E.
launchServiceCustomer
Indicates that a customer is the recipient or user of a launch service provided 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:16 a.m.