Triple
T12681403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLS solid rocket boosters |
E302954
|
entity |
| Predicate | burnProfile |
P106259
|
FINISHED |
| Object | high-thrust boost phase at liftoff |
—
|
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: high-thrust boost phase at liftoff | Statement: [SLS solid rocket boosters, burnProfile, high-thrust boost phase at liftoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burnProfile Context triple: [SLS solid rocket boosters, burnProfile, high-thrust boost phase at liftoff]
-
A.
burningSince
Indicates that an object or substance has been continuously burning from a specified starting time up to the present or another reference time.
-
B.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
-
C.
burnType
Indicates the specific category or severity of a burn associated with an entity or event.
-
D.
burnsWhen
Indicates that one entity causes another entity to ignite or combust when they come into contact or under specified conditions.
-
E.
burnMechanism
Indicates the process or mechanism by which burning or combustion occurs or is carried out.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b32dbc81908101fc5f07e26ed3 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:21 p.m.