Triple
T2833987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 1B |
E62305
|
entity |
| Predicate | thrustComparedToBlock1 |
P17733
|
FINISHED |
| Object | similar liftoff thrust to SLS Block 1 |
—
|
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: similar liftoff thrust to SLS Block 1 | Statement: [Block 1B, thrustComparedToBlock1, similar liftoff thrust to SLS Block 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustComparedToBlock1 Context triple: [Block 1B, thrustComparedToBlock1, similar liftoff thrust to SLS Block 1]
-
A.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
B.
thrustClass
chosen
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
C.
thrustAtSeaLevel
Indicates the amount of propulsive force an engine produces when operating at standard sea-level atmospheric conditions.
-
D.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
E.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.