Triple
T13426114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally1 |
E313485
|
entity |
| Predicate | allowsGearShiftSystem |
P88077
|
FINISHED |
| Object | mechanical gearshift only |
—
|
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: mechanical gearshift only | Statement: [Rally1, allowsGearShiftSystem, mechanical gearshift only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsGearShiftSystem Context triple: [Rally1, allowsGearShiftSystem, mechanical gearshift only]
-
A.
hasNumberOfGears
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
B.
gearSystemType
chosen
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
C.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
D.
usesGearboxFrom
Indicates that one entity operates or functions using a gearbox that originates from or is supplied by another entity.
-
E.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.