Triple
T12738587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch System Block 1B |
E304428
|
entity |
| Predicate | usesBoosters |
P103173
|
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: [Space Launch System Block 1B, usesBoosters, solid rocket boosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBoosters Context triple: [Space Launch System Block 1B, usesBoosters, solid rocket boosters]
-
A.
usedWithBoosters
chosen
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
-
B.
allowsBoosters
Indicates that one entity permits the use, presence, or activation of boosters in relation to another entity or context.
-
C.
numberOfBoosters
Indicates the quantity of booster units associated with or used by an entity.
-
D.
boosterRecommendation
Indicates that one entity advises or prescribes a booster (e.g., an additional dose or reinforcement) for another entity.
-
E.
boosterName
Indicates the name or designation assigned to a booster component associated with an entity or event.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.