Triple
T36835775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maybach OLVAR preselector gearbox |
E910266
|
entity |
| Predicate | gearChangeType |
P88077
|
FINISHED |
| Object | non-synchronized preselected gears |
—
|
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: non-synchronized preselected gears | Statement: [Maybach OLVAR preselector gearbox, gearChangeType, non-synchronized preselected gears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearChangeType Context triple: [Maybach OLVAR preselector gearbox, gearChangeType, non-synchronized preselected gears]
-
A.
gearChangeControl
Indicates the control action or mechanism responsible for changing gears within a system or device.
-
B.
gearSystemType
chosen
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
C.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
D.
drivetrainChangeDescription
Indicates a description of a modification or change made to a vehicle’s drivetrain system.
-
E.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.