Triple
T27996716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 first stage |
E707031
|
entity |
| Predicate | typicalBurnSequence |
P124160
|
FINISHED |
| Object | boostback burn |
—
|
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: boostback burn | Statement: [Falcon 9 first stage, typicalBurnSequence, boostback burn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBurnSequence Context triple: [Falcon 9 first stage, typicalBurnSequence, boostback burn]
-
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.
burnProfile
Indicates that one entity records or defines how another entity burns, such as its combustion characteristics or burn behavior.
-
C.
burnMode
Indicates that one entity is operating in or causing a state of intense, high-output, or destructive activity in another entity or process.
-
D.
burnTiming
chosen
Indicates the temporal characteristics or schedule associated with a burning event or burn-related process.
-
E.
burningIsCalled
Indicates that one entity refers to or names the act or state of burning by a particular term or label.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 27, 2026, 7:53 p.m.