Triple
T30136709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-120 |
E766013
|
entity |
| Predicate | guidanceRole |
P168478
|
FINISHED |
| Object | provides thrust vector control via gimbaling |
—
|
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: provides thrust vector control via gimbaling | Statement: [RD-120, guidanceRole, provides thrust vector control via gimbaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceRole Context triple: [RD-120, guidanceRole, provides thrust vector control via gimbaling]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another entity.
-
C.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
D.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
E.
guidanceComputer
Indicates that one entity functions as a guidance computer, providing navigational or control computations for another entity.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e4d0eec8190a25a9f6d74516857 |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:16 p.m.