Triple
T9413698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDPE-3A |
E226762
|
entity |
| Predicate | propulsionCapability |
P24153
|
FINISHED |
| Object | long‑duration on‑orbit propulsion |
—
|
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: long‑duration on‑orbit propulsion | Statement: [LDPE-3A, propulsionCapability, long‑duration on‑orbit propulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propulsionCapability Context triple: [LDPE-3A, propulsionCapability, long‑duration on‑orbit propulsion]
-
A.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
B.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
C.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
D.
propulsionTypeTested
Indicates that a specific type of propulsion has been subjected to testing or experimental evaluation.
-
E.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c680e48190be82e3829e8711f0 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.