Triple
T22134392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEM 63XL |
E546987
|
entity |
| Predicate | thrustAugmentation |
P106235
|
FINISHED |
| Object | increases liftoff thrust of Vulcan |
—
|
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: increases liftoff thrust of Vulcan | Statement: [GEM 63XL, thrustAugmentation, increases liftoff thrust of Vulcan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustAugmentation Context triple: [GEM 63XL, thrustAugmentation, increases liftoff thrust of Vulcan]
-
A.
thrustAugmentationMethod
chosen
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
-
B.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
C.
powerplantThrustClass
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
D.
totalThrust
Indicates the combined amount of thrust produced by one or more propulsion sources acting on an object or system.
-
E.
dryThrust
Indicates the amount of thrust an engine produces without the use of afterburner or additional augmenting systems.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b8f4248190b6342c8d00942c25 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.