Triple
T35575321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz EQC |
E1028058
|
entity |
| Predicate | ACChargingPowerMax |
P183417
|
FINISHED |
| Object | up to 11 kW |
—
|
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 11 kW | Statement: [Mercedes-Benz EQC, ACChargingPowerMax, up to 11 kW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ACChargingPowerMax Context triple: [Mercedes-Benz EQC, ACChargingPowerMax, up to 11 kW]
-
A.
fastChargingWattage
Indicates the maximum electrical power level at which a device can be charged using a fast-charging method.
-
B.
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.
-
C.
chargingNetworkCompatibility
Indicates that one entity’s charging system is compatible with, and can be used on, another entity’s charging network.
-
D.
chargingTime22kW
Indicates the duration required to charge an entity (typically a vehicle or battery) when using a 22 kW charging power.
-
E.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.