Triple
T30143198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Charging System |
E766180
|
entity |
| Predicate | usesConnectorStandard |
P1587
|
FINISHED |
| Object | IEC 62196-3 for DC |
—
|
NE NERFINISHED |
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: IEC 62196-3 for DC | Statement: [Combined Charging System, usesConnectorStandard, IEC 62196-3 for DC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConnectorStandard Context triple: [Combined Charging System, usesConnectorStandard, IEC 62196-3 for DC]
-
A.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
B.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
-
D.
usesACConnectorBase
Indicates that one entity employs or relies on another entity as its AC (alternating current) connector base.
-
E.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:18 p.m.