Triple
T1666924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin 1D |
E36032
|
entity |
| Predicate | gimbalRange |
P23303
|
FINISHED |
| Object | gimbaled for thrust vector control |
—
|
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: gimbaled for thrust vector control | Statement: [Merlin 1D, gimbalRange, gimbaled for thrust vector control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gimbalRange Context triple: [Merlin 1D, gimbalRange, gimbaled for thrust vector control]
-
A.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
B.
maxVerticalAngle
chosen
Indicates the greatest vertical angular difference or tilt between two entities or directions.
-
C.
tiltingCapability
Indicates the ability of one entity to tilt or be tilted relative to another or to a reference orientation.
-
D.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.