Triple
T19332552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F404-GE-400 |
E483531
|
entity |
| Predicate | hasThrustClass |
P22228
|
FINISHED |
| Object | approximately 16,000–17,000 lbf with afterburner |
—
|
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 16,000–17,000 lbf with afterburner | Statement: [F404-GE-400, hasThrustClass, approximately 16,000–17,000 lbf with afterburner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThrustClass Context triple: [F404-GE-400, hasThrustClass, approximately 16,000–17,000 lbf with afterburner]
-
A.
thrustClass
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
B.
powerplantThrustClass
chosen
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
C.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
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.