Triple
T19508487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powerbeats Pro |
E488087
|
entity |
| Predicate | fastChargeFeature |
P5893
|
FINISHED |
| Object | Fast Fuel |
—
|
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: Fast Fuel | Statement: [Powerbeats Pro, fastChargeFeature, Fast Fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastChargeFeature Context triple: [Powerbeats Pro, fastChargeFeature, Fast Fuel]
-
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.
fastChargingTime
Indicates the amount of time required to charge something (typically a battery or device) using a fast-charging method.
-
C.
flyCharge
Indicates that an entity is responsible for paying or incurring a fee associated with a flight.
-
D.
superchargerType
Indicates the specific kind or category of supercharger associated with or used by an entity.
-
E.
supportsAutoCharge
Indicates that one entity enables or is compatible with automatic charging functionality for 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6351426448190aec1ee26c09faa24 |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.