Triple
T27507663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotax 914F |
E694321
|
entity |
| Predicate | gearboxReductionRatio |
P162462
|
FINISHED |
| Object | 2.62:1 |
—
|
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: 2.62:1 | Statement: [Rotax 914F, gearboxReductionRatio, 2.62:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearboxReductionRatio Context triple: [Rotax 914F, gearboxReductionRatio, 2.62:1]
-
A.
gearboxReductionRatio
chosen
Indicates the ratio between the input speed and the output speed/torque provided by a gearbox.
-
B.
gearRatios
Indicates the proportional relationship between the rotational speeds or torques of interconnected gears in a mechanical system.
-
C.
rearAxleRatio
Indicates the numerical gear ratio between the driveshaft and the rear axle, describing how many driveshaft rotations are required for one rotation of the rear wheels.
-
D.
hasNumberOfGears
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
E.
gearboxLocation
Indicates the spatial position or placement of a gearbox relative to another object or reference frame.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef65ca88190b3e3b1c91d668843 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:14 p.m.