Triple
T12433008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney PW6000 |
E297077
|
entity |
| Predicate | thrustCategory |
P17733
|
FINISHED |
| Object | medium thrust turbofan |
—
|
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: medium thrust turbofan | Statement: [Pratt & Whitney PW6000, thrustCategory, medium thrust turbofan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustCategory Context triple: [Pratt & Whitney PW6000, thrustCategory, medium thrust turbofan]
-
A.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
B.
thrustClass
chosen
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
C.
thrustDistribution
Indicates how thrust or propulsive force is apportioned or spread among different components, directions, or stages within a system.
-
D.
thrustControl
Indicates a relationship where one entity regulates or adjusts the thrust output or propulsion force of another entity.
-
E.
thrustPhase
Indicates a phase in which a propulsion system is actively producing thrust as part of a larger operation or trajectory.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.