Triple
T17131661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-180 |
E415732
|
entity |
| Predicate | hasGuidanceControl |
P45638
|
FINISHED |
| Object | vectoring via gimbaled nozzles |
—
|
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: vectoring via gimbaled nozzles | Statement: [RD-180, hasGuidanceControl, vectoring via gimbaled nozzles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuidanceControl Context triple: [RD-180, hasGuidanceControl, vectoring via gimbaled nozzles]
-
A.
guidanceControl
Indicates that one entity directs, manages, or influences the behavior or decisions of another through guidance or control.
-
B.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
usesGuidanceKit
Indicates that one entity employs or relies on a guidance kit to direct, control, or navigate another entity or process.
-
D.
isGuided
Indicates that one entity is being directed, led, or steered in its actions or movement by another entity or influence.
-
E.
hasSteering
chosen
Indicates that one entity is equipped with or possesses a steering mechanism that allows control of its direction.
- 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.