Triple
T13246760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi i-MiEV |
E315424
|
entity |
| Predicate | chargingConnectorAC |
P10996
|
FINISHED |
| Object | Type 1 (J1772) |
—
|
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: Type 1 (J1772) | Statement: [Mitsubishi i-MiEV, chargingConnectorAC, Type 1 (J1772)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargingConnectorAC Context triple: [Mitsubishi i-MiEV, chargingConnectorAC, Type 1 (J1772)]
-
A.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
-
B.
chargingPortType
chosen
Indicates the specific kind of connector or interface used for charging a device.
-
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.
onboardACCharger
Indicates that an entity is equipped with an AC (alternating current) charger that is built into the system or vehicle itself.
-
E.
chargingModel
Indicates the pricing or billing scheme applied to an entity, such as how costs are calculated or charged.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5c09f88190bb1566a6d8c073a6 |
completed | April 10, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.