Triple
T25927044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW100 |
E653333
|
entity |
| Predicate | thrustOrPowerClass |
P22228
|
FINISHED |
| Object | 1,800 shp to over 5,000 shp |
—
|
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: 1,800 shp to over 5,000 shp | Statement: [PW100, thrustOrPowerClass, 1,800 shp to over 5,000 shp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustOrPowerClass Context triple: [PW100, thrustOrPowerClass, 1,800 shp to over 5,000 shp]
-
A.
powerplantThrustClass
chosen
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
B.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
C.
thrustClass
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
D.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
E.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6041473b08190a9b421b06f24b615 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:35 a.m.