Triple
T13315242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz 190E 2.3-16 |
E317173
|
entity |
| Predicate | gearboxType |
P88077
|
FINISHED |
| Object | Getrag dog-leg manual gearbox |
—
|
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: Getrag dog-leg manual gearbox | Statement: [Mercedes-Benz 190E 2.3-16, gearboxType, Getrag dog-leg manual gearbox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearboxType Context triple: [Mercedes-Benz 190E 2.3-16, gearboxType, Getrag dog-leg manual gearbox]
-
A.
gearboxLocation
Indicates the spatial position or placement of a gearbox relative to another object or reference frame.
-
B.
clutchType
Indicates the type or category of clutch mechanism associated with or used by an entity.
-
C.
hasNumberOfGears
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
D.
gearSystemType
chosen
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
E.
usesGearboxFrom
Indicates that one entity operates or functions using a gearbox that originates from or is supplied by 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.