Triple
T634045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCS (Combined Charging System) |
E15983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric vehicle charging standard |
C3599
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: electric vehicle charging standard Context triple: [CCS (Combined Charging System), instanceOf, electric vehicle charging standard]
-
A.
automotive terminal
An automotive terminal is an electrical connector component used in vehicles to securely join wires to each other or to devices within the automotive electrical system.
-
B.
power delivery specification
chosen
A power delivery specification defines the technical requirements, limits, and conditions under which electrical power must be supplied, distributed, and regulated within a system or between interconnected systems.
-
C.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
D.
telecommunications standard
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
E.
substation automation standard
A substation automation standard defines the protocols, architectures, and requirements that enable interoperable, secure, and automated monitoring, control, and protection of electrical substations.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 1, 2026, 7:35 p.m.