Triple
T17131665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-180 |
E415732
|
entity |
| Predicate | usedForPayloadClass |
P98
|
FINISHED |
| Object | medium-to-heavy payloads to LEO |
—
|
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: medium-to-heavy payloads to LEO | Statement: [RD-180, usedForPayloadClass, medium-to-heavy payloads to LEO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForPayloadClass Context triple: [RD-180, usedForPayloadClass, medium-to-heavy payloads to LEO]
-
A.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
B.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
C.
isKeyPayloadOf
Indicates that something functions as the primary or essential data component (key payload) within another entity or structure.
-
D.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.