Triple
T794177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissan Leaf |
E16980
|
entity |
| Predicate | electricMotorOutput |
P6069
|
FINISHED |
| Object | 80 kW (first generation, typical) |
—
|
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: 80 kW (first generation, typical) | Statement: [Nissan Leaf, electricMotorOutput, 80 kW (first generation, typical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricMotorOutput Context triple: [Nissan Leaf, electricMotorOutput, 80 kW (first generation, typical)]
-
A.
electricMotorType
Indicates the specific kind or category of electric motor associated with an entity.
-
B.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
D.
motorConfiguration
Indicates the specific arrangement, setup, or parameters defining how a motor is configured or operates within a system.
-
E.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.