Triple
T21815657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM 4L60-E |
E538599
|
entity |
| Predicate | gearRatios |
P145770
|
FINISHED |
| Object | 1st gear approximately 3.06: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: 1st gear approximately 3.06:1 | Statement: [GM 4L60-E, gearRatios, 1st gear approximately 3.06:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearRatios Context triple: [GM 4L60-E, gearRatios, 1st gear approximately 3.06:1]
-
A.
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.
-
B.
hasNumberOfGears
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
C.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
-
D.
cyclePerRotorRevolution
Indicates the number of complete cycles of a repeating event or signal that occur during one full revolution of a rotor.
-
E.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
- F. None of above. chosen
Provenance (4 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.