Triple
T36076343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Modell |
E1043504
|
entity |
| Predicate | typicalDriveLayouts |
P4169
|
FINISHED |
| Object | rear-wheel drive |
—
|
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: rear-wheel drive | Statement: [T-Modell, typicalDriveLayouts, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDriveLayouts Context triple: [T-Modell, typicalDriveLayouts, rear-wheel drive]
-
A.
driveLayoutSupported
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled by a given system or component.
-
B.
diskType
Indicates the specific kind or category of disk associated with or used by an entity.
-
C.
supportsDiskDrives
Indicates that one entity is capable of accommodating, operating, or being compatible with disk drives associated with another entity.
-
D.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
mechanicalDrive
Indicates a relationship where one entity transmits mechanical power or motion to another, typically via components like gears, belts, or shafts.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.