Triple
T33183312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-18 |
E849393
|
entity |
| Predicate | hasOnboardPropulsion |
P158578
|
FINISHED |
| Object | chemical propulsion system |
—
|
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: chemical propulsion system | Statement: [GSAT-18, hasOnboardPropulsion, chemical propulsion system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardPropulsion Context triple: [GSAT-18, hasOnboardPropulsion, chemical propulsion system]
-
A.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
B.
hasLiftOrLaunchSystem
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
-
C.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
D.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
propulsionTypeOfSystem
chosen
Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:29 a.m.