Triple
T13227966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | smart EQ forfour |
E314929
|
entity |
| Predicate | onboardChargerPower |
P5892
|
FINISHED |
| Object | 4.6 kW AC (standard) |
—
|
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: 4.6 kW AC (standard) | Statement: [smart EQ forfour, onboardChargerPower, 4.6 kW AC (standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardChargerPower Context triple: [smart EQ forfour, onboardChargerPower, 4.6 kW AC (standard)]
-
A.
onboardACCharger
chosen
Indicates that an entity is equipped with an AC (alternating current) charger that is built into the system or vehicle itself.
-
B.
chargingModel
Indicates the pricing or billing scheme applied to an entity, such as how costs are calculated or charged.
-
C.
chargingHandle
Indicates the component or action used to manually cycle or charge a firearm’s operating mechanism, typically to chamber a round or reset the bolt.
-
D.
chargingPortType
Indicates the specific kind of connector or interface used for charging a device.
-
E.
supportsChargingStandard
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.