Triple
T35636282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citroën C-Zero |
E1029728
|
entity |
| Predicate | standardChargingPower |
P183417
|
FINISHED |
| Object | 3.3 kW AC |
—
|
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: 3.3 kW AC | Statement: [Citroën C-Zero, standardChargingPower, 3.3 kW AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardChargingPower Context triple: [Citroën C-Zero, standardChargingPower, 3.3 kW AC]
-
A.
supportsChargingStandard
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
-
B.
fastChargingWattage
Indicates the maximum electrical power level at which a device can be charged using a fast-charging method.
-
C.
ACChargingPowerMax
chosen
Indicates the maximum electrical power that can be delivered to charge a device or system when using AC (alternating current).
-
D.
chargingModel
Indicates the pricing or billing scheme applied to an entity, such as how costs are calculated or charged.
-
E.
timeOfCharging
Indicates the specific time or period during which a charging event occurs.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:05 p.m.