Triple
T28427673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Eletre |
E715032
|
entity |
| Predicate | chargingPowerMax |
P4616
|
FINISHED |
| Object | up to 350 kW DC |
—
|
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: up to 350 kW DC | Statement: [Lotus Eletre, chargingPowerMax, up to 350 kW DC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargingPowerMax Context triple: [Lotus Eletre, chargingPowerMax, up to 350 kW DC]
-
A.
fastChargingCapability
Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
-
B.
maxPowerDelivery
chosen
Indicates the maximum amount of power that can be delivered from one entity to another under specified conditions.
-
C.
fastChargingTime
Indicates the amount of time required to charge something (typically a battery or device) using a fast-charging method.
-
D.
chargingTime22kW
Indicates the duration required to charge an entity (typically a vehicle or battery) when using a 22 kW charging power.
-
E.
chargingModel
Indicates the pricing or billing scheme applied to an entity, such as how costs are calculated or charged.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:37 a.m.