Triple
T9232330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LightSail 2 |
E221846
|
entity |
| Predicate | demonstratedCapability |
P87705
|
FINISHED |
| Object | orbit raising using solar radiation pressure |
—
|
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: orbit raising using solar radiation pressure | Statement: [LightSail 2, demonstratedCapability, orbit raising using solar radiation pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratedCapability Context triple: [LightSail 2, demonstratedCapability, orbit raising using solar radiation pressure]
-
A.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
developedCapability
Indicates that an entity has created, acquired, or brought into existence a particular capability through its actions or processes.
-
C.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
D.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
E.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1a7e9881908e0c11f242162017 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.