Triple
T20871424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M35A2 |
E513901
|
entity |
| Predicate | transmissionSpeeds |
P92307
|
FINISHED |
| Object | 5-speed main transmission |
—
|
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: 5-speed main transmission | Statement: [M35A2, transmissionSpeeds, 5-speed main transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionSpeeds Context triple: [M35A2, transmissionSpeeds, 5-speed main transmission]
-
A.
hasNumberOfGears
chosen
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
B.
transmissionModel
Indicates the mechanism or pattern by which something (such as information, disease, or signals) is passed or conveyed from one entity or location to another.
-
C.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4649cf88190b3ad946576aa46aa |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.