Triple
T29951880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enyaq iV |
E760788
|
entity |
| Predicate | numberOfMotorsOptions |
P201868
|
FINISHED |
| Object | single-motor and dual-motor options |
—
|
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: single-motor and dual-motor options | Statement: [Enyaq iV, numberOfMotorsOptions, single-motor and dual-motor options]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMotorsOptions Context triple: [Enyaq iV, numberOfMotorsOptions, single-motor and dual-motor options]
-
A.
numberOfMotors
Indicates the quantity of motors associated with or used by an entity.
-
B.
supportsMultipleMotorOutputs
Indicates that the subject is capable of driving or controlling more than one motor output simultaneously or in parallel.
-
C.
motorConfiguration
Indicates the specific arrangement, setup, or parameters defining how a motor is configured or operates within a system.
-
D.
electricMotorType
Indicates the specific kind or category of electric motor associated with an entity.
-
E.
numberOfEngines
Indicates the quantity of engines associated with or used by an entity.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 29, 2026, 6:26 p.m.