Triple
T36663904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Micro-A |
E905204
|
entity |
| Predicate | supportsDeviceCharging |
P170788
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USB Micro-A, supportsDeviceCharging, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeviceCharging Context triple: [USB Micro-A, supportsDeviceCharging, yes]
-
A.
supportsChargingMethod
Indicates that one entity is compatible with and can operate using a specified charging method.
-
B.
supportsChargingModel
Indicates that one entity is compatible with, or able to operate under, a specified charging or billing model.
-
C.
requiresCharging
Indicates that an entity depends on being recharged (e.g., with electrical power or energy) in order to function or continue operating.
-
D.
supportsChargingStandard
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
-
E.
hasUSBCharging
chosen
Indicates that one entity provides or supports USB-based power charging capability for another entity or device.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.