Triple
T8673625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Demo 2 |
E205859
|
entity |
| Predicate | usedSecondStageEngineType |
P8436
|
FINISHED |
| Object | NewtonFour |
—
|
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: NewtonFour | Statement: [Launch Demo 2, usedSecondStageEngineType, NewtonFour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSecondStageEngineType Context triple: [Launch Demo 2, usedSecondStageEngineType, NewtonFour]
-
A.
engineTypeSecondStage
chosen
Indicates the type or classification of the engine used in the second stage of a multi-stage system or vehicle.
-
B.
secondStageEngineManufacturer
Indicates that one entity is the manufacturer of the second-stage engine used by another entity (typically a launch vehicle or rocket).
-
C.
secondGenerationEngineOption
Indicates that an entity offers or is associated with a second-generation version of an engine as an available option.
-
D.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
E.
enginesUpperStage
Indicates that the specified engines are part of, or belong to, the upper stage of a multi-stage launch vehicle or rocket.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.