Triple
T19332577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RM12 |
E483532
|
entity |
| Predicate | afterburningThrust |
P106235
|
FINISHED |
| Object | approximately 80 kN |
—
|
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: approximately 80 kN | Statement: [RM12, afterburningThrust, approximately 80 kN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterburningThrust Context triple: [RM12, afterburningThrust, approximately 80 kN]
-
A.
AfterburnType
Indicates that one event, state, or process occurs as a subsequent or follow-up phase (an "afterburn") relative to another, typically extending or intensifying its effects.
-
B.
thrustAugmentationMethod
chosen
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
-
C.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
D.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
E.
totalThrust
Indicates the combined amount of thrust produced by one or more propulsion sources acting on an object or system.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61642f49c81909226cfd701f7c139 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.