Triple

T634080
Position Surface form Disambiguated ID Type / Status
Subject CCS (Combined Charging System) E15983 entity
Predicate supportsChargingMode P4636 FINISHED
Object Mode 3 AC charging 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: Mode 3 AC charging | Statement: [CCS (Combined Charging System), supportsChargingMode, Mode 3 AC charging]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsChargingMode
Context triple: [CCS (Combined Charging System), supportsChargingMode, Mode 3 AC charging]
  • 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. supportsPowerDelivery
    Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
  • C. supportsBidirectionalPower
    Indicates that an entity can both supply and receive power, allowing electrical energy to flow in either direction between connected systems.
  • D. definesPoweringMode chosen
    Indicates that one entity specifies or determines the operating or powering mode used by another entity.
  • E. hasPowerSource
    Indicates that an entity derives its operational energy or functionality from a specified power source.
  • 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_69a4935c131c8190a5378c6bf101e8cc completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49ee4ee8481908ad45405e3f3835c completed March 1, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69a49d0483908190a5ec42a7403c258e completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.