Triple
T35769936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huawei Nova 11 |
E1034130
|
entity |
| Predicate | hasChargingTechnology |
P93380
|
FINISHED |
| Object | Huawei SuperCharge |
—
|
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: Huawei SuperCharge | Statement: [Huawei Nova 11, hasChargingTechnology, Huawei SuperCharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargingTechnology Context triple: [Huawei Nova 11, hasChargingTechnology, Huawei SuperCharge]
-
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.
supportsChargingStandard
chosen
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
-
D.
hasUSBCharging
Indicates that one entity provides or supports USB-based power charging capability for another entity or device.
-
E.
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.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:06 p.m.