Triple
T12264918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Siddeley Pegasus |
E292317
|
entity |
| Predicate | typicalMaxThrust |
P29517
|
FINISHED |
| Object | around 23,800 lbf |
—
|
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: around 23,800 lbf | Statement: [Bristol Siddeley Pegasus, typicalMaxThrust, around 23,800 lbf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaxThrust Context triple: [Bristol Siddeley Pegasus, typicalMaxThrust, around 23,800 lbf]
-
A.
powerplantThrustClass
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
B.
thrustInVacuum_kN
Indicates the amount of propulsive force an engine produces in a vacuum, measured in kilonewtons.
-
C.
thrustAtSeaLevel
chosen
Indicates the amount of propulsive force an engine produces when operating at standard sea-level atmospheric conditions.
-
D.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
E.
maximumTakeoffWeight
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.