Triple
T30350710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-C310 |
E771980
|
entity |
| Predicate | hasQuickCharge |
P5893
|
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: [Sony WI-C310, hasQuickCharge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuickCharge Context triple: [Sony WI-C310, hasQuickCharge, yes]
-
A.
fastChargingCapability
chosen
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.
supportsChargingMethod
Indicates that one entity is compatible with and can operate using a specified charging method.
-
C.
supportsWirelessCharging
Indicates that one entity provides the capability for another entity to be charged without a physical wired connection, typically via inductive or similar wireless power transfer methods.
-
D.
supportsChargingStandard
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
-
E.
wirelessChargingStandard
Indicates that one entity specifies or supports the particular wireless charging protocol or standard used by another entity.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820b4b8c81908f5bbae956565ec0 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.