Triple
T17963715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen MEB platform |
E449147
|
entity |
| Predicate | supportsMultipleMotorOutputs |
P129933
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Volkswagen MEB platform, supportsMultipleMotorOutputs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleMotorOutputs Context triple: [Volkswagen MEB platform, supportsMultipleMotorOutputs, true]
-
A.
numberOfMotors
Indicates the quantity of motors associated with or used by an entity.
-
B.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
-
C.
hasPWMOutputs
Indicates that an entity provides or is associated with one or more PWM (pulse-width modulation) output signals.
-
D.
supportsMultipleBusMasters
Indicates that the system or component allows more than one bus master to control or access the bus concurrently or in turn.
-
E.
supportsMultiplePowerRoles
Indicates that an entity can simultaneously handle or be assigned more than one distinct power-related role.
- F. None of above. chosen
Provenance (4 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b135cd2c8190a6190cf6611dbe08 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.