Triple
T30968832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R tronic automated manual |
E789033
|
entity |
| Predicate | gearSelection |
P95343
|
FINISHED |
| Object | paddle shifters |
—
|
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: paddle shifters | Statement: [R tronic automated manual, gearSelection, paddle shifters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearSelection Context triple: [R tronic automated manual, gearSelection, paddle shifters]
-
A.
typicalGear
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
-
B.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
-
C.
gearSystemType
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
D.
equipmentOption
chosen
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
E.
recommendedEquipment
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.