Triple
T35643157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLS core stage |
E1029928
|
entity |
| Predicate | providesThrustWith |
P197341
|
FINISHED |
| Object | solid rocket boosters |
—
|
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: solid rocket boosters | Statement: [SLS core stage, providesThrustWith, solid rocket boosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesThrustWith Context triple: [SLS core stage, providesThrustWith, solid rocket boosters]
-
A.
totalThrust
Indicates the combined amount of thrust produced by one or more propulsion sources acting on an object or system.
-
B.
thrustType
Indicates the type or method of thrust or propulsion used in performing an action or driving a system.
-
C.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
D.
thrustCapability
Indicates the level or capacity of force an entity can exert to propel or push something, typically in a specified direction or context.
-
E.
thrustControl
Indicates a relationship where one entity regulates or adjusts the thrust output or propulsion force of 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: May 3, 2026, 4:05 p.m.