Triple
T5817697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-IC |
E129026
|
entity |
| Predicate | engineGimbalCapability |
P21233
|
FINISHED |
| Object | outer four engines gimbaled |
—
|
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: outer four engines gimbaled | Statement: [S-IC, engineGimbalCapability, outer four engines gimbaled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineGimbalCapability Context triple: [S-IC, engineGimbalCapability, outer four engines gimbaled]
-
A.
gimbalCapability
chosen
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
B.
apogeeCapability
Indicates the maximum altitude or apogee that an entity is capable of reaching or supporting.
-
C.
attitudeControlMethod
Indicates the technique or mechanism used to control or adjust the orientation or pointing direction of an object (such as a vehicle or device).
-
D.
tiltingCapability
Indicates the ability of one entity to tilt or be tilted relative to another or to a reference orientation.
-
E.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.