Triple
T14174513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM E2 platform |
E351297
|
entity |
| Predicate | driveConfigurationSupport |
P45176
|
FINISHED |
| Object | front-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: front-wheel drive | Statement: [GM E2 platform, driveConfigurationSupport, front-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveConfigurationSupport Context triple: [GM E2 platform, driveConfigurationSupport, front-wheel drive]
-
A.
driveModes
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
B.
driveLayoutSupported
chosen
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled by a given system or component.
-
C.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
E.
driveScheme
Indicates that one entity operates or controls a scheme, system, or initiative, causing it to function or move forward.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b7cc3081909f4fa371e1eae130 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.